-
Bug
-
Resolution: Done-Errata
-
Major
-
4.14.0
-
No
-
Hypershift Sprint 242
-
1
-
Proposed
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
After control plane release upgrade, and controlPlaneRelease field is removed in the HostedCluster CR, only capi-provider, cluster-api and control-plane-operator are restarted and run release image, other components are not restarted and still run control plane release image
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. create a cluster in 4.14-2023-09-06-180503 2. control plane release upgrade to 4.14-2023-09-07-180503 3. remove controlPlaneRelease in the HostedCluster CR 4. check all pods/containers images in the control plane namespace
Actual results:
only capi-provider, cluster-api and control-plane-operator are restarted and run release image 4.14-2023-09-06-180503, other components are not restarted and still run control plane release image 4.14-2023-09-07-180503. jiezhao-mac:hypershift jiezhao$ oc get hostedcluster -n clusters NAME VERSION KUBECONFIG PROGRESS AVAILABLE PROGRESSING MESSAGE jie-test 4.14.0-0.ci-2023-09-06-180503 jie-test-admin-kubeconfig Completed True False The hosted control plane is available jiezhao-mac:hypershift jiezhao$ - lastTransitionTime: "2023-09-08T01:54:54Z" message: '[cluster-api deployment has 1 unavailable replicas, control-plane-operator deployment has 1 unavailable replicas]' observedGeneration: 5 reason: UnavailableReplicas status: "True" type: Degraded
Expected results:
The control plane should return to release image 4.14-2023-09-06-180503 with all components in a healthy state.
Additional info:
