In 4.3 we found a serious bug that only existed when upgrading a cluster from 4.1 to 4.2 to 4.3. We should have an e2e test that verifies these upgrade paths. Create a test that performs sequential upgrades and backport to 4.3 and 4.4 so we can create the jobs. The jobs will select a representative build from each stream, and perform tests as we upgrade, and then at the very end we will run the e2e suite to ensure the cluster is fully functional.
Jobs are https://prow.svc.ci.openshift.org/job-history/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.1-to-4.2-to-4.3-to-4.4-nightly and https://prow.svc.ci.openshift.org/job-history/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.2-to-4.3-to-4.4-to-4.5-ci They run periodically. We will add others over time.
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-2020:0581