Description of problem: 1. For zVM hypervisor environments, OCP 4.10 nightly build 4.10.0-0.nightly-s390x-2021-12-17-144433 fails to upgrade from OCP 4.9.11 and 4.9.12 with the following failure message: 1. "oc get clusterversion" output: Unable to apply 4.10.0-0.nightly-s390x-2021-12-17-144433: wait has exceeded 40 minutes for these operators: cloud-controller-manager. 2. "oc get co" output Failed when progressing towards operator: 4.10.0-0.nightly-s390x-2021-12-17-144433 because &{%!e(string=failed to apply resources because CloudConfigControllerDegraded condition is set to True)} 2. This upgrade fails for both OVS (openshiftSDN) and OVN (OVNKubernetes) network types for both OCP 4.9.11 and 4.9.12. 3. Previous OCP 4.10 nightly build 4.10.0-0.nightly-s390x-2021-12-16-185334 succeeds for both OCP 4.9.11 and 4.9.12, for both OVS (openshiftSDN) and OVN (OVNKubernetes) network types. Version-Release number of selected component (if applicable): 1. OCP 4.9.11 upgrade to 4.10.0-0.nightly-s390x-2021-12-17-144433. 2. OCP 4.9.12 upgrade to 4.10.0-0.nightly-s390x-2021-12-17-144433. How reproducible: Consistently reproducible. Steps to Reproduce: 1. In zVM hypervisor environments, use OCP 4.9.11 or 4.9.12 CLI to attempt to upgrade to OCP 4.10 nightly build 4.10.0-0.nightly-s390x-2021-12-17-144433, using either OVS or OVN network types. Actual results: Upgrade fails with: 1. "oc get clusterversion" output: Unable to apply 4.10.0-0.nightly-s390x-2021-12-17-144433: wait has exceeded 40 minutes for these operators: cloud-controller-manager. 2. "oc get co" output Failed when progressing towards operator: 4.10.0-0.nightly-s390x-2021-12-17-144433 because &{%!e(string=failed to apply resources because CloudConfigControllerDegraded condition is set to True)} Expected results: Upgrade should succeed. Additional info: Thank you.
duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2033489
*** This bug has been marked as a duplicate of bug 2033489 ***