Skip to content

fix: cancel VMSS rolling upgrades before destroy - #1291

Merged
xinWeiWei24 merged 2 commits into
mainfrom
xinwei/fix-vmss-rolling-upgrade-destroy
Aug 18, 2026
Merged

fix: cancel VMSS rolling upgrades before destroy#1291
xinWeiWei24 merged 2 commits into
mainfrom
xinwei/fix-vmss-rolling-upgrade-destroy

Conversation

@xinWeiWei24

@xinWeiWei24 xinWeiWei24 commented Aug 18, 2026

Copy link
Copy Markdown
Collaborator

Azure-initiated VM Agent Rolling Upgrades can reject VMSS updates with OperationNotAllowed, causing AKS node resource group deletion to fail. Cancel them first so Terraform destroy can proceed.

Cancel in-progress VMSS rolling upgrades and back off retries to prevent Azure resource deletion failures.
@github-actions

Copy link
Copy Markdown

For reviewers only: reply /run-tf-integration to trigger the terraform integration pipeline before approving the PR.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR improves Azure teardown reliability by proactively canceling in-progress VMSS rolling upgrades that can prevent AKS node resource group deletion, and by adding a retry backoff when a rolling upgrade is still detected.

Changes:

  • Add a pre-destroy Azure step to cancel VMSS rolling upgrades in AKS node resource groups.
  • Add a 300-second backoff before task retry when Terraform logs indicate a rolling upgrade is still in progress.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread steps/terraform/run-command.yml Outdated
@xinWeiWei24
xinWeiWei24 merged commit 5c90f10 into main Aug 18, 2026
3 checks passed
@xinWeiWei24
xinWeiWei24 deleted the xinwei/fix-vmss-rolling-upgrade-destroy branch August 18, 2026 09:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants