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

[AWS][GHA] On-demand runners are not cleaning up correctly #44319

Closed
2 tasks
oseasmoran73 opened this issue Jul 13, 2022 · 6 comments
Closed
2 tasks

[AWS][GHA] On-demand runners are not cleaning up correctly #44319

oseasmoran73 opened this issue Jul 13, 2022 · 6 comments
Assignees
Labels
devops practice area categorization -- NOT a team assignment needs-grooming Use this to designate any issues that need grooming from the team platform-cop Issues that are in a Platform COP backlog platform-cop-devops for Platform CoP DevOps platform-cop-frontend for Platform CoP Frontend

Comments

@oseasmoran73
Copy link
Contributor

oseasmoran73 commented Jul 13, 2022

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

image


Tasks

  • If on-demand runners fail, all instances spun up should be properly shut down and terminated

Acceptance Criteria

  • Content-build workflow properly cleans up on-demand runners
@oseasmoran73 oseasmoran73 added operations devops practice area categorization -- NOT a team assignment needs-grooming Use this to designate any issues that need grooming from the team tools-fe Used for the frontend tools team labels Jul 13, 2022
@oseasmoran73
Copy link
Contributor Author

Adding slack convo

Would be great if we can get this prioritize in the next sprint or two @laineymajor

@mydesignrocks
Copy link
Contributor

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.
In the meantime, we will terminate the lingering unused ec2 on-demand runners, manually.

@olivereri
Copy link
Contributor

This can likely be closed to due to work in these issues:

Conent-build no longer uses on-demand runners:
department-of-veterans-affairs/va.gov-cms#11402

126 orphaned On-demand Content-build runners terminated:
department-of-veterans-affairs/va.gov-cms#11405

@oseasmoran73 oseasmoran73 added the platform-cop-frontend for Platform CoP Frontend label Apr 3, 2023
@oseasmoran73
Copy link
Contributor Author

oseasmoran73 commented Apr 3, 2023

@CBonade They should have all been cleaned up with the retries. Massive thanks to @olivereri for handling all those orphans from content-build!

I think the last step would be to sunset archive (preferably delete) that repository in its entirety to resources being orphaned. I will defer that to you as COP lead

Tasks

  • Reach out got Github Team to delete or archive repo
  • Final sanity check with AWS for orphaned content-build (rule of thumb, and > 30 days)

@CBonade
Copy link
Collaborator

CBonade commented Apr 6, 2023

https://github.com/department-of-veterans-affairs/github-user-requests/issues/15404 issue request here with GitHub opened to archive this repository.

@CBonade
Copy link
Collaborator

CBonade commented May 4, 2023

This was archived by the GitHub team so ready for closing.

@CBonade CBonade closed this as completed May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops practice area categorization -- NOT a team assignment needs-grooming Use this to designate any issues that need grooming from the team platform-cop Issues that are in a Platform COP backlog platform-cop-devops for Platform CoP DevOps platform-cop-frontend for Platform CoP Frontend
Projects
None yet
Development

No branches or pull requests

6 participants