Files
cozystack/internal
Myasnikov Daniil 195de033e8 fix(mariadb): pin legacy Backups to a proven dump, refuse failed runs
A Backup taken before Backups recorded their dump gives a restore
nothing to pin. Refusing such Backups would leave every existing one
unrestorable, so a restore of one now makes the same ownership-proven
match the backup side makes, against the operator Backup it names, and
restores that dump by its timestamp. When no dump can be proven to be
the run's own, or the storage cannot be read, mariadb-operator restores
the newest dump under the prefix as it always did, and a BestEffortDump
Warning on the RestoreJob says so and why.

An operator Backup whose Job failed is Complete=True with reason
JobFailed, and a BackupJob that took Complete=True for success made a
Backup of it. That run left no dump of its own, and restoring it would
quietly bring back another run's dump, so the RestoreJob now fails
instead. The condition is read by its reason, because its status does
not tell a failure from a success.

Assisted-by: LLM
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
2026-11-04 15:57:20 +00:00
..