-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.14.0
-
No
-
Hypershift Sprint 241
-
1
-
Rejected
-
False
-
Description of problem:
Changes to platform fields e.g. aws instance type doesn't trigger a rolling upgrade
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Create a hostedCluster with nodepool on AWS 2. Change the instance type field on the nodepool spec.platfrom.aws
Actual results:
Machines are not restarted and the instance type didn't change
Expected results:
Machines are recreated with the new instance type
Additional info:
This is a result of the recent changes to CAPI which introduced in-place propagation to labels and annotations Soultion: MachineTemplate name should not be constant and should change with each spec change, so that spec.infraRef in the MachineDeployment is updated and a rolling upgrade is triggered.
- is related to
-
HOSTEDCP-1133 NodePools should signal rolling upgrade because of platform changes
-
- Closed
-
- links to
-
RHEA-2023:5006
rpm
- mentioned on
[OCPBUGS-18127] Changes to NodePool .spec.platfrom doesn't trigger a rolling upgrade
GitLab CEE Bot
added a comment - Ian Main mentioned this issue in a merge request of Service Delivery / app-interface on branch ibm_integration_bump:
Bump IBM integration to our latest prod image.
GitLab CEE Bot
added a comment - Ian Main mentioned this issue in a merge request of Service Delivery / app-interface on branch ibm_integration_bump : Bump IBM integration to our latest prod image. Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Important: OpenShift Container Platform 4.14.0 bug fix and security update), and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:5006
Fixes currently on hold due to fixes possibly greatly increasing the API usage (there is a CI job that prevents API request rate from spiraling out of control)
Per the announcement sent regarding the removal of "Blocker" as an option in the Priority field, this issue (which was already closed at the time of the bulk update) had Priority = "Blocker." It is being updated to Priority = Critical. No additional fields were changed.