fix(reconciler): reconciler-next container can write its metrics (keep-id) (#202) #218
Inga granskare
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-infra!218
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "fix/reconciler-next-textfile-perms"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
Fixes an EACCES the ADR-0035 dry-run rehearsal (#202) surfaced: the
gitborg-reconciler-nextcontainer couldn't write its metrics file.The image runs as
node(uid 1000); rootless podman maps that to a subuid that can't write the bitborg-owned (0700) bind-mounted textfile dir →EACCES … reconciler.prom. AddingUserNS=keep-id:uid=1000,gid=1000maps the container's node user to the hostgitborguser, so it writes as the dir's owner; the dir stays bitborg-owned for node_exporter's read path.The reconcile logic itself already ran fine (the metric write is best-effort/WARN, and the dry-run proposed actions appear correctly in the journal) — this restores the metrics file, which is required before the step-4 flip to apply so
ReconcilerStalemonitoring works against the container. Syntax-check + ansible-lint (production) + Prettier clean.Refs #202, ADR 0035.