Skip to content
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

Merged

Conversation

feiskyer
Copy link
Member

@feiskyer feiskyer commented Apr 6, 2020

Cherry-pick #3023 and #3024 to CA 1.18:

  • Ensure VMSS is not under updating before scaling out
  • caches should be updated after async PUT succeeds

/kind bug
/area provider/azure

/cc @nilo19 @marwanad

@k8s-ci-robot k8s-ci-robot requested review from marwanad and nilo19 April 6, 2020 04:45
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. area/provider/azure Issues or PRs related to azure provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Apr 6, 2020
@marwanad
Copy link
Member

marwanad commented Apr 6, 2020

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

@feiskyer feiskyer changed the title CA 1.18: Caches should be updated after async PUT succeeds CA 1.18: Ensure VMSS is not under updating before scaling out Apr 6, 2020
@feiskyer
Copy link
Member Author

feiskyer commented Apr 6, 2020

@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
Copy link
Member

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?

Copy link
Member Author

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.

@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Apr 7, 2020
@marwanad
Copy link
Member

marwanad commented Apr 7, 2020

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 7, 2020
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 7, 2020
@k8s-ci-robot k8s-ci-robot merged commit 0c67f65 into kubernetes:cluster-autoscaler-release-1.18 Apr 7, 2020
@feiskyer feiskyer deleted the fix-cache branch April 7, 2020 04:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/provider/azure Issues or PRs related to azure provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants