Bug 1710494

Summary: Cloning CI ProwJobs to new releases reset their optional state
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: Test InfrastructureAssignee: Steve Kuznetsov <skuznets>
Status: CLOSED ERRATA QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: mifiedle, sponnaga
Target Milestone: ---   
Target Release: 4.1.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-04 10:48:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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.