ARC runners did not recover automatically after Github Outage
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 38/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions, go, helm, kubernetes
- Área
- ci-cd, devops, infrastructure
Línea de trabajo
Empieza leyendo el flujo de EphemeralRunnerReconciler y los logs vinculados del controlador y del runner, centrándote en los fallos de registro y en el backoff de BrokerServer después de que GitHub se recupere. Traza cómo se monitorizan actualmente los EphemeralRunners en ejecución y cómo se puede observar la validez del registro. Se considera terminado cuando se detectan los registros de GitHub no válidos, se limpian y se vuelven a aprovisionar los runners afectados, y el comportamiento de recuperación queda cubierto por pruebas.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
This is not reproducible directly as it is the byproduct of an incident.
see https://www.githubstatus.com/incidents/g9j4tmfqdd09
Describe the bug
During the GitHub Actions degraded availability incident on 2026-03-05 githubstatus.com/incidents/g9j4tmfqdd09), our ARC deployment experienced runners that became stuck in a bad state and were not automatically recovered after GitHub's services came back online.
These runners were registered before the incident, lost their registration during GitHub's degradation, and ARC never reconciled them back to a healthy state.
This was resolved by manually deleting all of the stuck ARC runner pods.
Describe the expected behavior
ARC has no garbage collection loop that reconciles GitHub-side runner registrations against actual Kubernetes pod state. The EphemeralRunnerReconciler only handles the forward path (create secret -> create pod -> monitor pod). It does not:
- Periodically verify that a runner's GitHub registration is still valid
- Detect runners whose registration was invalidated by a GitHub-side incident
- Clean up and re-provision runners that are running but no longer recognized by GitHub
I suggest that we should add periodic health check to the EphemeralRunnerReconciler that verifies the GitHub-side registration is still valid for running EphemeralRunners.
Additional Context
1. GitHub's `api.github.com/actions/runner-registration` endpoint became unavailable.
2. The ARC `EphemeralRunnerReconciler` failed to generate JIT configs for new runners, retrying 5 times with backoff before giving up.
3. Already-running runners lost their registrations on the GitHub side (`Registration <uuid> was not found`).
4. Runner pods entered `BrokerServer` backoff loops, unable to communicate with `broker.actions.githubusercontent.com`.
5. **After GitHub recovered at ~23:55 UTC, errors and backoff warnings continued until at least 00:17 UTC** — over 20 minutes of lingering failures. Runners that were mid-registration during the incident remained in a bad state with no automatic recovery.
Controller Logs
related logs:
https://gist.github.com/rob-howie-depop/27b15fd387ffc5f8f36e838614ffefc0
Runner Pod Logs
related logs:
https://gist.github.com/rob-howie-depop/27b15fd387ffc5f8f36e838614ffefc0
- 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
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
progress-deadline annotation accepts "0s" although validation says it must be positivePosiblemente ocupada @BahaaMattar la tomó hoy. Abiertoarea/API kind/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
api cleanup
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
router-for-me/CLIProxyAPI#7708 ·
Los mantenedores suelen responder en 1 día