Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

Do not update scaleset configs of halting scalesets #511

Merged

Conversation

bmc-msft
Copy link
Contributor

@bmc-msft bmc-msft commented Feb 5, 2021

This addresses an exception if a scaleset is set to have a configuration update after the scaleset deletion has started.

Example exception:

Exception: ResourceExistsError: (OperationNotAllowed) Operation 'Update Virtual Machine Scale Set' is not allowed on Virtual Machine Scale Set 'b242ea12-69e4-4984-90a5-c31b0d0b490a' since it is marked for deletion. For more information on your operations, please refer to https://aka.ms/activitylog.

Additionally, this will only update the configs if the scaleset has needs_config_update set.

@bmc-msft bmc-msft changed the title Scalesets that are about to be deleted don't need updated configs Do not update scaleset configs of halting scalesets Feb 5, 2021
@ghost
Copy link

ghost commented Feb 5, 2021

Hello @bmc-msft!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

Do note that I've been instructed to only help merge pull requests of this repository that have been opened for at least 18 hours, a condition that will be fulfilled in about 17 hours 31 minutes. No worries though, I will be back when the time is right! 😉

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@bmc-msft bmc-msft merged commit e3dfcb8 into microsoft:main Feb 5, 2021
@bmc-msft bmc-msft deleted the halted-scalesets-dont-need-updates branch February 5, 2021 14:53
@ghost ghost locked as resolved and limited conversation to collaborators Apr 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants