-
Notifications
You must be signed in to change notification settings - Fork 201
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
[AWS][GHA] On-demand runners are not cleaning up correctly #44319
Comments
Adding slack convo Would be great if we can get this prioritize in the next sprint or two @laineymajor |
update: all the workflows tied to content-build are migrated over to either self-hosted/asg or ubuntu-latest (github runner) with the exception of content-release. We are working with the respective teams to address the runner definition for the content-release in this sprint. That should resolve the requirement of this ticket. |
This can likely be closed to due to work in these issues: Conent-build no longer uses on-demand runners: 126 orphaned On-demand Content-build runners terminated: |
@CBonade They should have all been cleaned up with the retries. Massive thanks to @olivereri for handling all those orphans from I think the last step would be to Tasks
|
https://github.com/department-of-veterans-affairs/github-user-requests/issues/15404 issue request here with GitHub opened to archive this repository. |
This was archived by the GitHub team so ready for closing. |
Description
On-demand runners are not cleaning up correctly when retry occurs. If it is successful, then it will clean up that last successful one
Background/context
Repo
If you search in instances up and running in EC2, you will find on-demand runners that have not been spun down
Tasks
Acceptance Criteria
The text was updated successfully, but these errors were encountered: