+++ This bug was initially created as a clone of Bug #1753070 +++
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. It must be in 4.1 so we can run tests against master.
During investigation we identified a number of alerts that fire when a cluster is skewed that must also be skipped.
@Jessica, QE don't know how to verify this bugs. Could you help us verify it?
Verification will have to be done by Jessica since she is familiar with the test infrastructure.
We had another fix, Jessica has to reverify.
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.
There was an additional fix required.