-
Bug
-
Resolution: Done
-
Major
-
MCE 2.2.0, ACM 2.7.0
Description of problem:
I have created a hosted cluster on OCP 4.11.12. I have created several node pools that are OCP 4.10.z. When I try to upgrade one of those node pools without upgrading the cluster itself, then all other node pools that are upgradable are also selected, and I can't select any node pools without selecting the cluster first.
Upon opening the upgrade modal (by clicking my intended node pool to upgrade):
And then selecting the node pool I want to upgrade (should be auto checked since I clicked upgrade on this specific pool?):
And then unselecting the cluster causes all the boxes to be checked:
Version-Release number of selected component (if applicable):
2.7.0-DOWNSTREAM-2022-11-15-16-49-09
How reproducible:
always
Steps to Reproduce:
- create an upgradeable hosted cluster, go to node pools in overview page
- create node pool A with a lower version than the chosted control plane
- create node pool B with lower version than the hosted control plane
- Select "upgrade available" for pool A
- Try to upgrade pool A without upgrading HCP, observe issues.
- Additionally, if you click on upgrade anyway (lets say all the node pools are selected, but not the HCP... in other words, i want to bring my node pools up to the HCP version), nothing happens.
Actual results:
Expected results:
Additional info:
- relates to
-
ACM-1745 Implement upgrade modal for AWS Hypershift clusters
- Closed