-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.16.z, 4.19.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
Unspecified
-
None
-
None
-
None
-
CLOUD Sprint 275, CLOUD Sprint 276, CLOUD Sprint 277, CLOUD Sprint 278
-
4
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When coming from an Openshift cluster with no failureDomains defined, after changing the infrastructure object with new failureDomains, the Machine objects for new and old Nodes don't properly get updated with the new regions and zones
Version-Release number of selected component (if applicable):
4.16.z
How reproducible:
Reproduced it twice, once in 4.16 and once in 4.19
Steps to Reproduce:
1. Create a cluster with zero or one failureDomain 2. Edit the infrastructure object as mentioned in the documentation [1] 3. Create a new MachineSet to observe if the Machines get assigned with the right labels.
[1]: Multiple regions and zones configuration for a cluster on VMware vSphere
Actual results:
When checking the Machine objects, the labels for zone and region of both the new and old Machines are empty.
Expected results:
The labels should get assigned to the corresponding zone and region fetching them from the respective vCenter's tags.
Additional info: