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.
We found an additional test that needs to be covered under this. Jessica will verify.
Hi Clayton,you changed version from 4.2.0 to 4.2.z,did you intend to change target release version?
Yes I did, we need to deliver this fix into 4.2.z
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.
Verified this is included in most recent nightly builds https://openshift-release.svc.ci.openshift.org/releasestream/4.2.0-0.nightly/release/4.2.0-0.nightly-2019-09-27-191818?from=4.2.0-0.nightly-2019-09-24-194016
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