-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Critical
-
None
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Please change component if this is not the correct area
Description of problem:
I have a 3 node Rosa HCP cluster that I put some load on and started an upgrade. The upgrade cluster command finished and I saw operators and overall cluster version upgrade properly. When I am trying to upgrade the machinepool I see no progress being seen after over an hour.
Version-Release number of selected component (if applicable):
4.17.0-rc.5
How reproducible:
100%
Steps to Reproduce:
1. Create 3 node multiaz Rosa HCP cluster
2. Load cluster with kube-burner-ocp (cluster-density-v2 workload with 10 iterations)
3. Upgrade cluster: rosa upgrade cluster -y -m auto --version 4.17.0-rc.5 -c 2e0u2j2jobn10lok6dsmg7lvs4urts6s --control-plane
4. Wait for upgrade to finish and upgrade machinepools
rosa upgrade machinepool workers-0 -y -c 2e0u2j2jobn10lok6dsmg7lvs4urts6s --version 4.17.0-rc.5
rosa upgrade machinepool workers-1 -y -c 2e0u2j2jobn10lok6dsmg7lvs4urts6s --version 4.17.0-rc.5
rosa upgrade machinepool workers-2 -y -c 2e0u2j2jobn10lok6dsmg7lvs4urts6s --version 4.17.0-rc.5
5. Machinepools never update
Actual results:
Machinepools never update, the machine pools scheduled update time passes and no progress seems to be done
Expected results:
Upgrade and upgraded machine pools get to wanted version with all operators and nodes ready
Additional info:
Details of cluster during machine pools trying to update. %rosa list machinepool --cluster sdq-longname-evtvb-xnsexixaycfjnuqyxpjxwmumrxhstbpjtig ID AUTOSCALING REPLICAS INSTANCE TYPE LABELS TAINTS AVAILABILITY ZONE SUBNET DISK SIZE VERSION AUTOREPAIR workers-0 Yes 1/1-1 m5.xlarge us-west-2c subnet-00e106c25cb9ec639 150 GiB 4.16.13 Yes workers-1 Yes 1/1-1 m5.xlarge us-west-2a subnet-0281f0fe441bbcc14 150 GiB 4.16.13 Yes workers-2 Yes 1/1-1 m5.xlarge us-west-2b subnet-060fece8fe9a2175f 150 GiB 4.16.13 Yes % oc get co NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE console 4.17.0-rc.5 True False False 61m csi-snapshot-controller 4.17.0-rc.5 True False False 11m dns 4.17.0-rc.5 True False False 61m image-registry 4.17.0-rc.5 True False False 61m ingress 4.17.0-rc.5 True False False 61m insights 4.17.0-rc.5 True False False 62m kube-apiserver 4.17.0-rc.5 True False False 70m kube-controller-manager 4.17.0-rc.5 True False False 70m kube-scheduler 4.17.0-rc.5 True False False 70m kube-storage-version-migrator 4.17.0-rc.5 True False False 62m monitoring 4.17.0-rc.5 True False False 20m network 4.17.0-rc.5 True False False 69m node-tuning 4.17.0-rc.5 True False False 11m openshift-apiserver 4.17.0-rc.5 True False False 70m openshift-controller-manager 4.17.0-rc.5 True False False 70m openshift-samples 4.17.0-rc.5 True False False 11m operator-lifecycle-manager 4.17.0-rc.5 True False False 70m operator-lifecycle-manager-catalog 4.17.0-rc.5 True False False 70m operator-lifecycle-manager-packageserver 4.17.0-rc.5 True False False 70m service-ca 4.17.0-rc.5 True False False 62m storage 4.17.0-rc.5 True False False 11m % oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.17.0-rc.5 True False 5m Cluster version is 4.17.0-rc.5