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
One of the delays for understanding the incident in dotnet/arcade#13774 was our inability to know what was causing the 1es hosted pool agents to provision correctly. We had a signal that agents were unhealthy, but no way to track down the reason, so we relied on an ICM and directly engaging with the on call engineer to find out that it was a core quota problem.
We should reach out to the 1ES team to see if there's a self-service way to obtain this information. I couldn't find anything obvious in the Troubleshooting & support pages in https://aka.ms/1eshostedpools
Release Note Category
Feature changes/additions
Bug fixes
Internal Infrastructure Improvements
Release Note Description
The text was updated successfully, but these errors were encountered:
One of the delays for understanding the incident in dotnet/arcade#13774 was our inability to know what was causing the 1es hosted pool agents to provision correctly. We had a signal that agents were unhealthy, but no way to track down the reason, so we relied on an ICM and directly engaging with the on call engineer to find out that it was a core quota problem.
We should reach out to the 1ES team to see if there's a self-service way to obtain this information. I couldn't find anything obvious in the Troubleshooting & support pages in https://aka.ms/1eshostedpools
Release Note Category
Release Note Description
The text was updated successfully, but these errors were encountered: