Skip to content

Fix repeated installation for Azure and GCP VM auto-discovery#32361

Merged
atburke merged 1 commit intomasterfrom
atburke/auto-discovery-node-filter
Sep 26, 2023
Merged

Fix repeated installation for Azure and GCP VM auto-discovery#32361
atburke merged 1 commit intomasterfrom
atburke/auto-discovery-node-filter

Conversation

@atburke
Copy link
Copy Markdown
Contributor

@atburke atburke commented Sep 21, 2023

This PR fixes a bug where the keys of labels applied to discovered Azure and GCP VMs did not match the labels the Discovery Service expected, causing the Discovery Service to try to install them again.

This PR also adds a workaround for an Azure quirk where Azure would not run the same command more than once.

Fixes #28879.

// won't run them more than once. This is fine when the installer script
// succeeds, but it makes troubleshooting much harder when it fails. To
// work around this, we generate a random string and append it as a comment
// to the script, forcing Azure to see each invocation as unique.
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.

Ouch

@atburke atburke added this pull request to the merge queue Sep 26, 2023
Merged via the queue into master with commit 042d56e Sep 26, 2023
@atburke atburke deleted the atburke/auto-discovery-node-filter branch September 26, 2023 16:18
@public-teleport-github-review-bot
Copy link
Copy Markdown

@atburke See the table below for backport results.

Branch Result
branch/v12 Failed
branch/v13 Create PR
branch/v14 Create PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Azure VM auto-discovery keeps executing commands after successful installation

3 participants