-
Bug
-
Resolution: Done-Errata
-
Undefined
-
OADP 1.2.3, OADP 1.3.1
-
False
-
-
False
-
oadp-operator-bundle-container-1.3.1-35
-
ToDo
-
-
-
0
-
0
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
No
Description of problem:
dpa.spec.configuration.velero.args.garbage-collection-frequency has wrong description. As per upstream docs garbage collection runs every hour by default.
https://velero.io/docs/v1.13/how-velero-works/#set-a-backup-to-expire
Version-Release number of selected component (if applicable):
OADP 1.3.1
How reproducible:
Always
Steps to Reproduce:
1.
Actual results:
garbage-collection-frequency has a wrong default frequency
$ oc explain dpa.spec.configuration.velero.args.garbage-collection-frequency KIND: DataProtectionApplication VERSION: oadp.openshift.io/v1alpha1 FIELD: garbage-collection-frequency <integer> DESCRIPTION: How long to wait by default before backups can be garbage collected. (default 720h0m0s)
Expected results:
gc-controller runs its reconciliation loop every hour by default.
Additional info:
- relates to
-
OADP-3355 [DOC] Release Notes for OADP 1.3.1
- Closed
- links to
-
RHSA-2024:126995 OpenShift API for Data Protection (OADP) 1.3.1 security and bug fix update