fix(ci): fall back to ghcr.io when the registry cache is unavailable - #2695
Closed
shikanime wants to merge 1 commit into
Closed
fix(ci): fall back to ghcr.io when the registry cache is unavailable#2695shikanime wants to merge 1 commit into
shikanime wants to merge 1 commit into
Conversation
The playwright init step pulls application images from the internal pull-through cache registry-cache-ghcr:5000. Since 2026-09-07 the cache serves HTTP 500 on blob transfer, blocking the whole merge queue while branch CI stays green and upstream ghcr.io serves the same tags anonymously. Pull each image from the cache, and on failure emit a warning annotation and pull directly from ghcr.io so the queue self-heals while the platform owners restore the cache. Refs #2694 Co-authored-by: Automata <automata@shikanime.studio> Signed-off-by: William Phetsinorath <william.phetsinorath-open@interieur.gouv.fr> Change-Id: I6035050c7d666c84b08ae7a16a1ef0486a6a6964
|
0 New Issues
0 Fixed Issues
0 Accepted Issues
No data about coverage (24.80% Estimated after merge)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issues liées
#2694
Quel est le comportement actuel ?
L'étape
Initialize application environment for testsdu workflow Playwright tire les 5 images applicatives exclusivement depuis le registre de cache interneregistry-cache-ghcr:5000.Depuis le 2026-09-07, ce cache répond
500 Internal Server Errorau transfert des blobs : chaque runMerge Queueéchoue sur les 4 shards, alors que la CI de branche reste verte et queghcr.iosert les mêmes tags anonymement.Quel est le nouveau comportement ?
Chaque image est d'abord tirée depuis le cache ; en cas d'échec, un avertissement
::warning::est émis et le pull est retenté directement surghcr.io, avant l'étiquetagedso-console/<img>:ciinchangé.La file de merge se rétablit donc seule pendant que le cache est indisponible, et l'annotation rend chaque bascule visible dans les logs du job.
Le coût nominal est nul : en régime établi le cache répond et le comportement reste identique.
Cette PR introduit-elle un breaking change ?
Non.
Autres informations
Le correctif est un containment côté workflow ; le rétablissement du service
registry-cache-ghcr(pod + stockage) reste à instruire par les owners plateformegithubrunners, voir le commentaire d'analyse sur #2694.