Actions
Bug #24825
closedCleanup after unsucessful backup attempt is not 100% accurate with previously nonexistent destination
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Description
This is a minor issue happening when creating a backup in previously nonexistent directory, e.g.:
foreman-maintain backup online test
...
Check if the directory exists and is writable: [FAIL]
Postgres user needs write access to the backup directory
Please allow the postgres user write access to /root/test/satellite-backup-2018-09-05-07-19-14 or choose another directory.
...
Running Failed backup cleanup
Clean up backup directory: [OK]
However, only satellite-backup* is cleaned up, /root/test/ remains created.
On the other hand, doing the same with --preserve-directory:
foreman-maintain backup online --preserve-directory test2
...
Prepare backup Directory:
Creating backup folder /root/test2 [OK]
--------------------------------------------------------------------------------
Check if the directory exists and is writable: [FAIL]
Backup directory (/root/test2) does not exit.
--------------------------------------------------------------------------------
...
Running Failed backup cleanup
...
Clean up backup directory: [SKIPPED]
Backup directory will be preserved
--------------------------------------------------------------------------------
Here /root/test2 is not even created, despite the preservation message
Actions