redhat-developer / redhat-developer/mapt
[CI] Investigate why a sleep is needed after adding a runner for it to start accepting jobs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
While working on #282 we found that scheduling a job immediately after adding the self-hosted runner, the runner would not accept the job, this was worked around by adding a sleep to create an artificial delay between adding the runner and submitting the first job for that runner, we should investigate why this delay is needed.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/provision-hosted-runner.yaml at the linked lines 60-61 and inspect how the runner is added before the first job is submitted. Reproduce the sequence with and without the sleep, then determine why the runner is not immediately accepting jobs. Done means the startup behavior is understood and the artificial delay can be removed or replaced with a reliable approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100