-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.12
-
None
-
None
-
False
-
Description of problem:
Attempting to upgrade a ROSA cluster from 4.12 to 4.13 before making the administrator acknowledgement for deprecated Kubernetes APIs causes the upgrade to hang indefinitely. https://docs.redhat.com/en/documentation/openshift_container_platform/4.13/html/updating_clusters/updating-cluster-prepare#update-preparing-ack_updating-cluster-prepare
Version-Release number of selected component (if applicable):
4.12
Steps to Reproduce:
1. Initiate ROSA cluster upgrade from 4.12 to 4.13 without performing acknowledgement. 2. Observe that the cluster gets stuck and never upgrades, even after making the admin acks and the Managed Upgrade Operator times out.
Actual results:
Cluster gets stuck here: NAME DESIRED_VERSION PHASE STAGE STATUS REASON MESSAGE managed-upgrade-config 4.13.48 Upgrading IsClusterUpgradable False IsClusterUpgradable not done Cluster upgrade to version 4.13.48 on Fri Sep 6 16:09:52 UTC 2024 has been cancelled: MultipleReasons: Cluster should not be upgraded between minor versions for multiple reasons: AdminAckRequired,Degraded
Expected results:
Cluster upgrades successfully after admin acknowledgement is made like this: $ oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.12-kube-1.26-api-removals-in-4.13":"true"}}' --type=merge
Additional info:
Only workaround at the moment is for SRE to manually cancel the upgrade and try again.