-
Notifications
You must be signed in to change notification settings - Fork 4k
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
CA 1.18: Ensure VMSS is not under updating before scaling out #3025
CA 1.18: Ensure VMSS is not under updating before scaling out #3025
Conversation
can you update the commit message and PR title to "Ensure VMSS is not under updating before scaling out" since that's the bigger part of the change |
@marwanad Good catch. Updated and PTAL |
klog.Errorf("VMSS %q is still under updating, waiting for it finishes before scaling", scaleSet.Name) | ||
return fmt.Errorf("VMSS %q is still under updating", scaleSet.Name) | ||
} | ||
|
||
// Update the new capacity to cache. | ||
vmssSizeMutex.Lock() | ||
vmssInfo.Sku.Capacity = &size |
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.
update the provision state in cache here?
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.
weird, seems some changes have been lost with last commit. Fixed now.
caches after async PUT succeeds.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: marwanad The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Cherry-pick #3023 and #3024 to CA 1.18:
/kind bug
/area provider/azure
/cc @nilo19 @marwanad