fix(backup-drill): avoid restic repo-lock collision with the storage backup (#219) #220
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!220
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "fix/backup-drill-restic-lock"
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 #219 — the weekly restore drill fails (
BackupDrillFailed, exit 11) when it overlaps the daily storage-tier restic backup's exclusive repo lock.backup_drill_on_calendarSat 05:00 → Sat 06:00 (the daily storage backup at 05:00 finishes in ~3 min).--retry-lock=10mon the drill's restic wrapper (restore-on-scratch.sh) so a concurrent backup is waited out, not fatal.Root cause + Loki timeline in #219. Backups and the restore path are healthy — the backup snapshot saved cleanly and the drill restored Postgres + the data volume fine before hitting the lock; purely a scheduling/lock-timing collision introduced by the storage-tier restic decoupling (#188/#211).
After merge + apply, a manual off-peak drill will confirm green and clear the alert.
ansible:check,ansible-lint(production), Prettier clean.Closes #219.