owned this note   changed 3 years ago  
Published Linked with GitHub

Jakob's Ruck Rover Robot

tags: ruck_rover

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →
DO NOT EDIT THIS FILE! CHANGES WILL BE OVERWRITTEN!
Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

RDO Cockpit / RHOS Cockpit

RDO Promoter / RHOS Promoter

OpenStack Program Meeting 2022

Zuul Status:

Help

The purpose of this page is

  • to save time by automating repetitive tasks such as listing failed jobs and identifying failure reasons and
  • to increase sample size of failed jobs for a given hash to help identifying consistent vs intermittent bugs vs transient failures.

This page is automatically generated by Jakob's Ruck Rover Robot, so please:

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →
DO NOT EDIT THIS FILE! CHANGES WILL BE OVERWRITTEN!
Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

Instead, copy content over to your current ruck and rover notes and start investigating failures based on that. Now, let us dive into what this page provides.

First, it shows a UTC timestamp indicating the last script execution:

2038-01-19 (Tuesday) 03:14 (UTC)

Next comes a preformatted section for Reruns and Investigations which is meant to be copied to current ruck and rover notes. It provides links to Zuul's status pages on review.rdoproject.org and sf.hosted.upshift.rdu2.redhat.com.

Reruns and Investigations:

(crossed out := known bugs recorded above)

NOTE: Watch for running testproject jobs on https://review.rdoproject.org/zuul/status and https://sf.hosted.upshift.rdu2.redhat.com/zuul/t/tripleo-ci-internal/status.

The Reruns and Investigations section consists of a subsection for Integration Lines and a subsection for Component Lines.

Integration Lines

This sections gives a status report for all integration lines, from centos-9 master down to rhel-8 osp16-2. Each top-level list entry is a hyperlink which points to its corresponding Grafana Dashboard aka Cockpit. Each entry shows the latest promotion date, the hash under consideration, a list of failed jobs in criteria and a list of pending jobs in criteria. Each job name itself is a link which takes us to Zuul's build history of that job. Below the job name the latest failure reason is printed which is again a link that takes you to the job's log.

Component Lines

The status report for component lines is similar to equivalent for integration lines. Main difference is that only components are listed which have failed criteria jobs.

Last but not least: Good luck with your ruck and rover shift!

2022-10-14 (Friday) 13:49 (UTC)

Reruns and Investigations:

(crossed out := known bugs recorded above)

NOTE: Watch for running testproject jobs on https://review.rdoproject.org/zuul/status and https://sf.hosted.upshift.rdu2.redhat.com/zuul/t/tripleo-ci-internal/status.

Integration Lines

Component Lines

Select a repo