401 bad credentials when attempting to create a runner registration token #106360
Replies: 1 comment
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
This is an issue that I'm having with Actions Runner Controller, and I've created a question here under ARC discussions. However, the error I'm seeing is due to a 401 response from the GH API:
This happens when ARC attempts to create a runner registration token for https://github.com/pytorch/xla using a GH app I created under a test org here: https://github.com/apps/tpu-ci-test.
What I believe is happening is that because the GH app I created (under the org https://github.com/bzmarke-test-org) was not created under the same org as the repo I'm attempting to get a runner registration token for (https://github.com/pytorch), I'm getting a 401 response, even though the GH app has all the necessary permissions (repo admin read & write, org self-hosted runners read & write, metadata read), and has been installed in the pytorch org.
Can someone please confirm this is the case? Does the GH app need to be under the same org as the repo?
Beta Was this translation helpful? Give feedback.
All reactions