replace Windows agents #5527
Merged
replace Windows agents #5527
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It looks like the change in Windows agent names has caused an issue: because Windows agents are not always properly cleaned up on shutdown, i.e. they do not always have time to tell Azure they are going away, and because GCP likes to reuse the same names for machines in a group, we've been seeing errors like: ``` ERROR: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Pool 11 already contains an agent with name VSTS-WIN-3QCX. ``` recently. Today, only 2 out of our 6 agents have managed to register with Azure. This PR should fix that. ChaNGELOG_BEGIN CHANGELOG_END
|
Since we seem to have a bit of activity still tonight, I'm going to manually repair the current situation (i.e. delete "failed" agents from Azure then delete the corresponding machines on GCP). |
hurryabit
approved these changes
Apr 9, 2020
|
Can confirm we're back to 6 working agents. Will keep an eye on this tomorrow and merge over the weekend. |
|
Just deployed 08a5a64 and confirmed everything is working. (As well as before, at least.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It looks like the change in Windows agent names has caused an issue: because Windows agents are not always properly cleaned up on shutdown, i.e. they do not always have time to tell Azure they are going away, and because GCP likes to reuse the same names for machines in a group, we've been seeing errors like:
recently. Today, only 2 out of our 6 agents have managed to register with Azure. This PR should fix that.
ChaNGELOG_BEGIN
CHANGELOG_END