Bug 1710494 - Cloning CI ProwJobs to new releases reset their optional state
Summary: Cloning CI ProwJobs to new releases reset their optional state
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Test Infrastructure
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.1.0
Assignee: Steve Kuznetsov
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2019-05-15 16:01 UTC by Clayton Coleman
Modified: 2019-06-04 10:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-06-04 10:48:48 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0758 0 None None None 2019-06-04 10:49:49 UTC

Description Clayton Coleman 2019-05-15 16:01:09 UTC
The config that sets some jobs as optional (because ci-operator config doesn't record that) was lost when new jobs were cloned to the release-4.1 branches, causing a large number of jobs that are not required to be required (launch-aws, e2e-vsphere).

We need to either manually update these jobs to have the correct optional/always_run settings, or move the optional/always_run config to ci-operator and have the generator.

The optional jobs need to be disabled quickly on release-4.1 so that we don't block fixes going into that branch.

Comment 1 Steve Kuznetsov 2019-05-15 18:12:59 UTC
Fixed https://github.com/openshift/release/pull/3806

Comment 3 errata-xmlrpc 2019-06-04 10:48:48 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.