[release-1.12] 🐛 fix: use machine's .spec.failureDomain with fallback to vspheremachine's .spec.failureDomain if not defined #3589
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Manual cherry-pick of #3576
This commit sets failureDomain string defaulting to
machine.Spec.FailureDomain
. If failureDomainis an empty string then
vsphereMachine.Spec.FailureDomain
is checked for nil, if definedfailureDomain
is set tovsphereMachine.Spec.FailureDomain
.This resolves an issue where virtual machines are not placed within vm-host groups in a timely
manner causing misplacement in the topology.