-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
OADP 1.1.1
-
False
-
-
False
-
ToDo
-
-
-
Important
-
8
-
0
-
Very Likely
-
0
-
Customer Escalated, Customer Facing
-
None
-
Unset
-
Unknown
-
No
Description of problem:
The prehook feature for OADP is supposed to pause to allow pre backup job to complete. Unfortunately the backup job continues to run before the prehook completes. This is despite the prehook being given lots of time to complete.
The prehook feature is documented here from a Red Hat viewpoint -> https://docs.openshift.com/container-platform/4.11/backup_and_restore/application_backup_and_restore/backing_up_and_restoring/backing-up-applications.html#oadp-creating-backup-hooks_backing-up-applications
See "Creating Backup Hooks". In the yaml there is a timeout that can be set to allow the hook to complete. This is point 10 in the document.
Below is the yaml from the mysql deployment config in production. The relevant section is
annotations:
pre.hook.backup.velero.io/command: >-
["/bin/bash", "-c", "mkdir -p /var/lib/mysql/data/backups && export
MYSQL_PWD=${MYSQL_ROOT_PASSWORD} && mysqldump --single-transaction
-hsystem-mysql -uroot system | gzip >
/var/lib/mysql/data/backups/system-mysql-backup-$(date +'%A').gz"]
pre.hook.backup.velero.io/container: system-mysql
pre.hook.backup.velero.io/timeout: 240s
Note this line pre.hook.backup.velero.io/timeout: 240s.
Version-Release number of selected component (if applicable):
OADP 1.1
How reproducible:
100%
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: