Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate how to investigate individual 1ES hosted pool agent provisioning errors. #175

Open
3 tasks
riarenas opened this issue Jun 8, 2023 · 0 comments
Open
3 tasks

Comments

@riarenas
Copy link
Member

riarenas commented Jun 8, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants