UnprocessableEntity from 'POST https://api.github.com/repos/myorganization/myproject/actions-runners/registration'
See original GitHub issueDescribe the bug
- Run Create registration token method of github API
- Pass token from the response to config.sh
- Runner authentication fails with message
Http response code: UnprocessableEntity from 'POST https://api.github.com/repos/myorganization/myproject/actions-runners/registration'
{"message":"Validation Failed","documentation_url":"https://developer.github.com/v3"}
Response status code does not indicate success: 422 (Unprocessable Entity).
An error occurred: Not configured
This error does not reproduce if I push the button Add runner from project settings before any API calls. After pushing this button runner authentication works pretty well event with tokens generated with API. For me it looks like this button also changes some flag in project settings.
To Reproduce Steps to reproduce the behavior:
- Create a new repo
- Call the rest api to create a registration token for a new runner
- Use that token with config.sh in to setup and run a new runner in the recently created repo.
- The error will be given.
Expected behavior I would expect to be able to do the above steps without having to manually go into the interface first and click the “Add Runner” button in the repo settings.
Runner Version and Platform
Any version
OS of the machine running the runner? OSX/Windows/Linux/… Any OS
Here is a thread in the community with the exact same issue: https://github.community/t5/GitHub-Actions/Self-hosted-runners-API-Unprocessable-Entity/td-p/47098
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top GitHub Comments
@tpinniger, adding you to this issue as you will be interested when it’s fixed.
👋 This issue should now be fixed. Runner registration should now work correctly for new repositories that have not used Actions yet or created any workflows.
Thank you for finding this issue.