The use of Github App results in "403 Resource not accessible by integration"
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- azure, github-actions, go, helm, kubernetes
- Área
- authentication, ci-cd, devops, infrastructure
Línea de trabajo
Comienza con TROUBLESHOOTING.md, la configuración values.yaml del chart de Helm y los logs del controlador en el gist enlazado; compara la configuración de GitHub App que falla con la configuración de PAT que funciona. Reproduce la respuesta 403 y la terminación del runner pod; después, verifica que se complete correctamente cuando la autenticación de GitHub App funcione y el runner pod se inicie correctamente.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- Lenguaje dominante
- Go
- Estrellas
- 6.7k
- Forks
- 1.5k
- Merge medio
- 1 h 34 min
- PR fusionados (30 d)
- 5
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de actions/actions-runner-controller
-
community enhancement needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
actions/actions-runner-controller#3997 · 9 comentarios · 27 reacciones ·
Los mantenedores suelen responder en 1 día
-
Surface the Outdated phase, and tell a runner version deprecation apart from a rejected specAbierto
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
actions/actions-runner-controller#4739 · 1 comentario · 4 reacciones ·
Los mantenedores suelen responder en 1 día
-
gha-runner-scale-set: support Google Cloud Secret Manager as a vault for GitHub credentialsPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertocommunity enhancement needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
actions/actions-runner-controller#4737 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Controller upgrade cancels jobs that started shortly before their runner set is deletedQuizá libre de nuevo @ankit373 la tomó hace 9 días y no hay ningún pull request abierto. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
actions/actions-runner-controller#4736 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
EphemeralRunnerSet controller creates more runners than `spec.replicas` when its cache lags its own createsPosiblemente ocupada @jia-pylon la tomó hace 14 días. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 30/100
actions/actions-runner-controller#4734 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de actions/actions-runner-controller
Issues similares
-
benchmark
Dificultad 1/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
mozilla-ai/cq#601 ·
Los mantenedores suelen responder en 1 día
-
documentation migration
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día