Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug] Build image cbdb-build-rocky9-latest: dnf fails on Rocky minor-version transitions due to pinned 9.7 baseurls

Aperta
  • Qualcosa non va?
#1,709 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
docker, linux
Ambito
ci-cd, devops, infrastructure

Direzione di ricerca

Individua il Dockerfile o il punto di ingresso della build dell’immagine che produce apache/incubator-cloudberry:cbdb-build-rocky9-latest, quindi esamina /etc/yum.repos.d/rocky*.repo nell’immagine. Riproduci il problema con dnf install -y glibc-langpack-de e confronta gli URL dei repository con la transizione di Rocky 9 descritta. Il lavoro è completato quando l’immagine ricostruita installa i pacchetti senza 404 dei mirror 9.7 e rimane utilizzabile per il workflow CI a cui si fa riferimento.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

type: Bug
Apache Cloudberry version

cloudberry 2.1.x /2.0.x

What happened

Summary

The CI build image apache/incubator-cloudberry:cbdb-build-rocky9-latest
ships dnf repository files with baseurl paths pinned to a specific
Rocky Linux minor version (currently 9.7). Whenever Rocky publishes
the next point release (now 9.8), upstream mirrors stop serving the
old minor — the previous tree is moved to vault.rockylinux.org. From
that moment, every dnf install inside the image fails with hundreds of
404s on *-modules.yaml.xz, *-primary.xml.gz, *-filelists.xml.gz,
etc. This breaks any downstream CI that does runtime package installs
on top of this image, including apache/cloudberry-backup.

What you think should happen instead

Root cause

/etc/yum.repos.d/rocky*.repo (or the mirrorlist= URLs they generate)
embed the minor version 9.7 instead of the rolling major 9 (or
$releasever mapped to 9). Mirror network behavior on Rocky point
releases has been consistent for years: only the current minor is on
live mirrors; older minors move to vault.rockylinux.org.

Proposed fixes (any one is sufficient)

  1. Rolling major in baseurl (preferred). Change repo baseurl
    from .../rocky/9.7/... to .../rocky/9/... (or rely on the
    mirrorlist= form that Rocky's official rocky.repo uses, which
    resolves the current point release automatically). This makes the
    image resilient across future 9.x → 9.y transitions without any
    maintenance.
  2. Rebuild image on Rocky 9.8 base. Short-term unblock, but the
    same problem will recur at 9.9.
  3. Add vault.rockylinux.org as a fallback baseurl. Keeps the
    pinned-minor model working after the transition. Slower than live
    mirrors but always available.

In addition, it would help downstream CIs if commonly required locale
packages were pre-installed in the image (e.g.
glibc-langpack-de, glibc-langpack-en), so that a transient mirror
outage upstream doesn't cascade into every Cloudberry-related test job.

Impact

Until the image is republished, every CI run against
apache/cloudberry-backup (and likely any other repo using this image
plus a runtime dnf install) will fail at the package-install step,
regardless of code changes in the PR. We are currently working around
it by rewriting the repo files to point at vault.rockylinux.org in
the workflow itself, but that is brittle and not appropriate as a
long-term fix.

Happy to send a PR against whichever Dockerfile produces this image if
the maintainers can point me at it.

How to reproduce

Reproduction

Inside a fresh container of apache/incubator-cloudberry:cbdb-build-rocky9-latest:

dnf install -y glibc-langpack-de                                                                                                                                      
                                                          
fails with:

Errors during downloading metadata for repository 'appstream':
  - Status code: 404 for http://.../rocky/9.7/AppStream/x86_64/os/repodata/...                                                                                        
Error: Failed to download metadata for repo 'appstream'                                                                                                               
                                                                                                                                                                      
(All ~40 mirrors in the mirrorlist 404 because none of them carry 9.7/                                                                                                
on the live tree anymore.)                                                                                                                                            
                                                                                                                                                                      
Real CI failure for reference:                            
- Repo: apache/cloudberry-backup                                                                                                                                      
- Workflow: cloudberry-backup-ci.yml, step Setup Locale for Integration Tests                                                                                         
- Symptom: dnf install -y glibc-langpack-de fails with the 404 storm above 

### Operating System

rockyLinux 9.x



### Code of Conduct

- [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/cloudberry/blob/main/CODE_OF_CONDUCT.md).
Lingua principale
C
Stelle
1.4k
Fork
248
Merge medio
4g 10h
PR unite (30g)
40

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/cloudberry

Tutte le issue di apache/cloudberry

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.