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

Continually try updating scaleset configs until successful #489

Merged
merged 1 commit into from
Feb 1, 2021

Conversation

bmc-msft
Copy link
Contributor

As is, if a scaleset is "failed" for some reason (such as Azure VM allocation failed), the service does not attempt to push updated VM configs, which can cause our time-limited SAS tokens in the VM config to timeout.

This PR makes 2 changes:

  1. attempts to perform any update as long as the scaleset isn't in the "Updating" state
  2. moves the config update attempts from once per day configured once per day, but runs every 90 seconds until it's successful.

@bmc-msft bmc-msft merged commit 0f70ffa into microsoft:main Feb 1, 2021
@bmc-msft bmc-msft deleted the try-updating-frequently branch February 1, 2021 15:09
@ghost ghost locked as resolved and limited conversation to collaborators Apr 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants