@Gabe the s390x nightly payload has been cleaned up from https://openshift-release.svc.ci.openshift.org/. Do I just need install a x86_64 cluster, and switch to s390x architure to check if there are still x86_64 images installed, just like I did in the card https://jira.coreos.com/browse/DEVEXP-418?
This is actually no change from the jira issue, we just needed the bug in order to cherry-pick the change back to 4.2.z, so if you are comfortable w/ the validation you already did for the jira ticket you can simply move this to verified.
As the test in the jira card, set samples operator to Removed, then change Architectures to s390x and state to Managed. The clusteroperator openshift-samples show: status: conditions: - lastTransitionTime: "2019-11-26T08:07:51Z" reason: NonX86Platform status: "True" type: Available - lastTransitionTime: "2019-11-26T08:07:51Z" reason: NonX86Platform status: "False" type: Progressing - lastTransitionTime: "2019-11-26T08:07:51Z" reason: NonX86Platform status: "False" type: Degraded And no x86_64 image installed under openshift project. Verified with 4.3.0-0.nightly-2019-11-24-183610
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:0062