Create full backup (juju run postgresql/leader create-backup)
Restore it (juju run postgresql/leader restore backup-id=<your_value>)
Expected behavior
After successful restore, cluster should print message "Restore succeeded" in the debug-log and Patroni restart condition should be restored.
Actual behavior
Cluster appears in the "Move restored cluster to another S3 bucket" and it indicates, that restore process is finished. But there is no "Restore succeeded" message in the debug-log and Patroni restart condition isn't really restored - juju show-unit postgresql/0 shows related fields:
I've found specific commit that causes this issue: ac88aca4849043ee7cec19dbdf768a41b3e45ae6 (#521). I think this issue will be critical when working on Timelines management for the PITR.
github-actions[bot]
commented
2 months ago
Steps to reproduce
juju run postgresql/leader create-backup)juju run postgresql/leader restore backup-id=<your_value>)Expected behavior
After successful restore, cluster should print message "Restore succeeded" in the debug-log and Patroni restart condition should be restored.
Actual behavior
Cluster appears in the "Move restored cluster to another S3 bucket" and it indicates, that restore process is finished. But there is no "Restore succeeded" message in the debug-log and Patroni restart condition isn't really restored -
juju show-unit postgresql/0shows related fields:Overall, it leads to the conclusion, that successful restore does not trigger all its events and does not restore cluster to the fully working state.
Versions
Operating system: Ubuntu 24.04 LTS
Juju CLI: 3.5.3-genericlinux-amd64
Juju agent: 3.5.3
Charm revision: from ~ 436 to current (456)
LXD: 6.1
Log output
Juju debug log: current rev - vm_is_restore_finished_backupid.log, before commit - vm_is_restore_finished_precommit_backupid.log
Additional context
I've found specific commit that causes this issue: ac88aca4849043ee7cec19dbdf768a41b3e45ae6 (#521). I think this issue will be critical when working on Timelines management for the PITR.