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.

Sign up for GitHub

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

Jump to bottom

[github] orphaned VMs/handler job, not registered to github actions #40

Open
NorseGaud opened this issue Dec 5, 2024 · 2 comments
Open

[github] orphaned VMs/handler job, not registered to github actions #40

NorseGaud opened this issue Dec 5, 2024 · 2 comments
Assignees
@NorseGaud

Comments

@NorseGaud
Copy link
Member

Looks like there is a problem with github actions that's causing VMs/runners to not register to github and the job and VM to be orphaned.

https://github.com/orgs/community/discussions/146348

Please upvote this and report it through Enterprise support if your company has it.
@NorseGaud NorseGaud self-assigned this Dec 5, 2024
@NorseGaud NorseGaud pinned this issue Dec 5, 2024
@NorseGaud NorseGaud changed the title Orphaned VMs/handler job, not registered to github actions [github] orphaned VMs/handler job, not registered to github actions Dec 5, 2024
NorseGaud added a commit that referenced this issue Dec 11, 2024
@NorseGaud
SplitByPlugin for logs so it's easier to troubleshoot and do dev + ha…
e365436 
…ndling in_progress so we can use it to check if the registration happened in a certain time and work around #40 failures and retry
@NorseGaud
Copy link
Member Author

actions/runner#3621

@NorseGaud
Copy link
Member Author

In 0.10.0 we will work around this.

At the moment of writing this, Github has a bug that assigns the same internal ID to runners that are registered around the same time. See actions/runner#3621 for more info. This means we need to count the time between when we register and start the runner in the VM and when the webhook/job goes into in_progress status, indicating the job in Github is now running inside of the VM properly. IF it doesn't go into in_progress within 1 minute, we consider it the github bug and will retry it on a brand new VM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@NorseGaud NorseGaud

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@NorseGaud