-
Notifications
You must be signed in to change notification settings - Fork 59
🐛Move volumecheck below ReconfigureVM #1255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛Move volumecheck below ReconfigureVM #1255
Conversation
9f28778 to
12c86b9
Compare
8d231ac to
4ccd360
Compare
4ccd360 to
60d47ae
Compare
60d47ae to
5dd47a9
Compare
f531a50 to
1263b42
Compare
1263b42 to
1ef41dd
Compare
Minimum allowed line rate is |
| Message: "cannot add/edit/remove controllers when the VM is powered on", | ||
| } | ||
| if moVM.Runtime.PowerState != vimtypes.VirtualMachinePowerStatePoweredOff { | ||
| // This shouldn't happen since validating webhook should've blocked this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW this could happen b/c we can't know the VM's actual power state in the webhook
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then do you think it's more appropriate to error and emit a condition on VM?
What does this PR do, and why is it needed?
Right now order between volume check and reconciling virtual controllers is incorrect. Adding virtualcontrollers need to happen before volume check.
So
Which issue(s) is/are addressed by this PR? (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Are there any special notes for your reviewer:
Please add a release note if necessary: