Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done-Errata
Priority: Critical
Fix Version/s: 4.15.0
Affects Version/s: 4.14.0
Component/s: HyperShift
Labels:

Regression:
No
Sprint:
Hypershift Sprint 241
sprint_count:
1
Release Blocker:
Rejected
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Target Version:

4.14.0

SFDC Cases Counter:
SFDC Cases Links:

Description

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.