Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1753070

Summary: Tests must allow skipping certain platform invariants to do node skew testing
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: Test InfrastructureAssignee: Clayton Coleman <ccoleman>
Status: CLOSED ERRATA QA Contact: Mike Fiedler <mifiedle>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: jforrest, mifiedle, wsun, xtian
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1753071 1756108 (view as bug list) Environment:
Last Closed: 2019-10-16 06:41:33 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:
Embargoed:
Bug Depends On: 1756108    
Bug Blocks: 1753071    

Description Clayton Coleman 2019-09-18 02:34:40 UTC
A 4.1 cluster test suite needs to be able to run against a 4.2 control plane with 4.1 nodes in a way that is reproducible for automation. For now, we'll create a "half" payload for 4.2 that excludes machine-config and then use the 4.1 suite. The test suite needs to ignore two specific tests that verify that every operator in the cluster has the same version (machine-config will be 4.1) and one that checks the images are all in the current payload.  That will enable the skew tests to use 4.1.

Fixing in 4.2 and then backporting to 4.1.

Comment 3 Clayton Coleman 2019-09-22 22:53:46 UTC
We found an additional test that needs to be covered under this.  Jessica will verify.

Comment 4 Wei Sun 2019-09-24 09:08:29 UTC
Hi Clayton,you changed version from 4.2.0 to 4.2.z,did you intend to change target release version?

Comment 5 Clayton Coleman 2019-09-25 17:30:15 UTC
Yes I did, we need to deliver this fix into 4.2.z

Comment 8 Jessica Forrester 2019-09-26 19:45:44 UTC
Putting this back to 4.2.0 since we technically haven't created the 4.2.0 GC yet, even though this code doesn't directly deliver into the product.

Comment 11 errata-xmlrpc 2019-10-16 06:41:33 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.

https://access.redhat.com/errata/RHBA-2019:2922