The use of Github App results in "403 Resource not accessible by integration"
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Bug
- Chiarezza
- Da chiarire
- Stato di attività
- Ferma
- Stack tecnologico
- azure, github-actions, go, helm, kubernetes
- Ambito
- authentication, ci-cd, devops, infrastructure
Direzione di ricerca
Inizia con TROUBLESHOOTING.md, la configurazione values.yaml del chart Helm e i log del controller nel gist collegato; confronta la configurazione GitHub App che non funziona con quella PAT funzionante. Riproduci la risposta 403 e la terminazione del runner pod, quindi verifica il completamento quando l’autenticazione GitHub App funziona e il runner pod si avvia correttamente.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Checks
- I've already read https://github.com/actions/actions-runner-controller/blob/master/TROUBLESHOOTING.md and I'm sure my issue is not covered in the troubleshooting guide.
- I'm not using a custom entrypoint in my runner image
Controller Version
0.27.6
Helm Chart Version
0.23.7
CertManager Version
1.12.1
Deployment Method
Helm
cert-manager installation
I have followed the instructions here:https://github.com/actions/actions-runner-controller/blob/master/docs/installing-arc.md
Cert-manager is working fine.
Checks
- This isn't a question or user support case (For Q&A and community support, go to Discussions. It might also be a good idea to contract with any of contributors and maintainers if your business is so critical and therefore you need priority support
- I've read releasenotes before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes
- My actions-runner-controller version (v0.x.y) does support the feature
- I've already upgraded ARC (including the CRDs, see charts/actions-runner-controller/docs/UPGRADING.md for details) to the latest and it didn't fix the issue
- I've migrated to the workflow job webhook event (if you using webhook driven scaling)
Resource Definitions
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
name: azure-github-runner
namespace: azure-github-runner
resourceVersion: "667378852"
uid: 6640c03a-39b7-498e-8ec1-e117bf2143b6
spec:
replicas: 1
template:
spec:
dockerEnabled: false
dockerdWithinRunnerContainer: false
# we have pushed the public image to our private Azure Container Registry
image: <REDACTED>.azurecr.io/summerwind/actions-runner:v2.319.1-ubuntu-22.04-1be410b
labels:
- azure-github-runner-prod
repository: <REDACTED>/ansible-gitlab
status:
availableReplicas: 1
desiredReplicas: 1
readyReplicas: 1
replicas: 1
updatedReplicas: 1
To Reproduce
See description below ("Describe the bug")
Describe the bug
Hi, I am trying to use Github App as the authentication method, but currently this results in an error "403 Resource not accessible by integration". The PAT authentication method works without problems. Here are the details:
--Setup
aks cluster: v1.28.9
actions-runner-controller helm chart version: 0.23.7
controller-image version: 0.27.6
--Description
I am trying to configure actions-runner-controller (with a Helm chart) to run Github actions from a repository (one single repository) in my Github organization (for this Organization I have an owner role). Everything works fine when I configure a PAT token, but when I try to replace the PAT token with a Github App (under the organization, not by using my personal account) I run into the following error: "403 Resource not accessible by integration" . As per my understanding the Github App configuration in Github as well as the values.yaml file for the helm chart installation have been configured correctly:
Github App (which is owned by the organization) has the following permissions:
-Repository Permissions: Actions (read + write), Checks (read + write), Contents (read + write), Metadata (read), Workflows (read + write)
-Organization Permissions: Self-hosted runners (Read + write)
Any help on this issue would be highly appreciated. Thank you.
Describe the expected behavior
I would be able to use the Github App authentication method instead of PAT.
Whole Controller Logs
https://gist.github.com/taneli-kantomaa/5067ee88a322465c08a7282a18c2fc99
Whole Runner Pod Logs
The runner pod does not start at all (or then it starts, but terminates immediately).
Additional Context
No response
- Lingua principale
- Go
- Stelle
- 6.7k
- Fork
- 1.5k
- Merge medio
- 1h 34m
- PR unite (30g)
- 5
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di actions/actions-runner-controller
-
community enhancement needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
actions/actions-runner-controller#3997 · 9 commenti · 27 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
actions/actions-runner-controller#4739 · 1 commento · 4 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
gha-runner-scale-set: support Google Cloud Secret Manager as a vault for GitHub credentialsForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertacommunity enhancement needs triage
Difficoltà 4/5 3-5 giorni Idoneità per principianti 52/100
actions/actions-runner-controller#4737 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Controller upgrade cancels jobs that started shortly before their runner set is deletedForse di nuovo libera @ankit373 l’ha presa 9 giorni fa e non c’è nessuna pull request aperta. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
actions/actions-runner-controller#4736 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
EphemeralRunnerSet controller creates more runners than `spec.replicas` when its cache lags its own createsForse già presa @jia-pylon l’ha presa 14 giorni fa. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 30/100
actions/actions-runner-controller#4734 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di actions/actions-runner-controller
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
mozilla-ai/cq#601 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno