actions / actions/actions-runner-controller
gha-runner-scale-set-0.13.1 installation fails with RunnerScaleSetNotFoundException
Open
Nobody has claimed this yet.
bug
gha-runner-scale-set
needs triage
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
Checks
- I've already read https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors and I'm sure my issue is not covered in the troubleshooting guide.
- I am using charts that are officially provided
Controller Version
0.13.1
Deployment Method
Helm
Checks
- This isn't a question or user support case (For Q&A and community support, go to Discussions).
- I've read the Changelog before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes
To Reproduce
Install 0.12.1, then upgrade to 0.13.1
Describe the bug
After upgrade, listeners are not getting ready:
Application returned an error: createSession failed: failed to create session: failed to do the session request: actions error: StatusCode 404, ActivityID "xxx" Github.Actions.Runtime.WebApi.RunnerScaleSetNotFoundException, Github.Actions.Runtime.WebApi: No runner scale set found with identifier 22.
Describe the expected behavior
listener get ready and helm upgrade succeeds.
Additional Context
K8s 1.32
GHES 3.16
Controller Logs
.
Runner Pod Logs
.
Contributor guide
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 by reproducing the Helm upgrade from 0.12.1 to 0.13.1 on Kubernetes 1.32 with GHES 3.16, then examine the listener failure and RunnerScaleSetNotFoundException. Done means the listeners become ready and the Helm upgrade succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go, helm, kubernetes
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100