-
Bug
-
Resolution: Done-Errata
-
Minor
-
4.14
-
Important
-
No
-
Hypershift Sprint 242, Hypershift Sprint 243, Hypershift Sprint 244, Hypershift Sprint 245, Hypershift Sprint 246
-
5
-
Rejected
-
False
-
-
-
Bug Fix
-
Done
Description of problem:
There is currently no way to interrupt a stuck HostedCluster upgrade because we don't allow another upgrade until the current upgrade is finished. At the very least we should allow overriding the upgrade with the ForceUpgradeTo annotation.
The function name doesn't honour the behaviour.
Version-Release number of selected component (if applicable):
4.14
How reproducible:
Always
Steps to Reproduce:
1. Install hosted cluster 2. Start upgrade to a bad release that will not complete 3. Attempt to override the current upgrade with a different release via annotation.
Actual results:
The override upgrade is not applied because the initial upgrade is not completed.
Expected results:
The override upgrade starts and completes successfully.
Additional info:
https://github.com/openshift/hypershift/blob/572a75655f0d86d6e2139f27e14eb1b168a5842b/hypershift-operator/controllers/hostedcluster/hostedcluster_controller.go#L4123-L4135
- links to
-
RHEA-2023:7198 rpm
-
RHSA-2023:5006 OpenShift Container Platform 4.14.z security update
- mentioned on