You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We were affected by a recent Azure outage (Tracking ID: VVTQ-J98). After this outage we noticed that we couldn't start Windows VM agents with the following error message: Disk win16sql17-a2-os already exists in resource group TEAMCITY-BUILD-AGENTS. Only CreateOption.Attach is supported
Does this plugin clean up resources if the agent did not start successfully?
Could you use a more unique naming convention to prevent this issue from happening again?
Description
We were affected by a recent Azure outage (Tracking ID: VVTQ-J98). After this outage we noticed that we couldn't start Windows VM agents with the following error message:
Disk win16sql17-a2-os already exists in resource group TEAMCITY-BUILD-AGENTS. Only CreateOption.Attach is supportedDoes this plugin clean up resources if the agent did not start successfully?
Could you use a more unique naming convention to prevent this issue from happening again?
Environment
The text was updated successfully, but these errors were encountered: