-
Notifications
You must be signed in to change notification settings - Fork 676
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
[Bug Fix] Fix hanging after name update when vm shutdown, fix null po… #5881
[Bug Fix] Fix hanging after name update when vm shutdown, fix null po… #5881
Conversation
if d.HasChange(Arg_InstanceName) && d.HasChange(Arg_VirtualOpticalDevice) { | ||
oldVOD, _ := d.GetChange(Arg_VirtualOpticalDevice) | ||
d.Set(Arg_VirtualOpticalDevice, oldVOD) | ||
return diag.Errorf("updates to %s and %s are mutually exclusive", Arg_InstanceName, Arg_VirtualOpticalDevice) | ||
} |
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.
Updates are mutually exclusive for name/active vm resources and cloud initialization, so an error is thrown here (clarification comment).
if err != nil { | ||
return nil, "", err | ||
} | ||
if strings.ToLower(*pvm.Status) == State_Active && pvm.Health.Status == OK { |
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.
You would also need to check the Arg_HealthStatus
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.
Added only to active block. Kept shutoff the same since the other update function also only checks for "OK" health status when checking for shutdown (keeps behavior the same).
901bf06
to
f9ff13c
Compare
…inter error when updating VOD
f9ff13c
to
4bb2d85
Compare
Community Note
Description:
Output from acceptance testing:
pi_instance (r)