backup-drill: restore drill selects the restic/ dir instead of the latest archive #213
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!213
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "fix/drill-fetch-skips-restic-dir"
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?
Problem
The restore drill failed on its first run after the storage decoupling.
fetch_latest_archive()lists the off-site bucket with
rclone lsf … --include "bitborg-*.tar.age"and takesmax()of thenames to pick the newest archive. But the restic storage repo now lives under a
restic/prefix inthe same Glesys bucket, and
lsfalso lists that directory.restic/sorts lexicographicallyafter
bitborg-*, somax()selectedrestic/— the drill then copied the whole ~9 GB restictree into its workdir and
age -dfailed ("is a directory"). Left unfixed, the weekly drill wouldfail the same way (→
BackupDrillFailed) and leave a multi-GB orphan on the backup volume each run.Fix
Add
--files-onlyto therclone lsfcall so directory prefixes aren't listed, and defensivelykeep only
.tar.agenames beforemax(). Follow-up to #211/#212.Impact
the drill selects to restore.