Details
-
Bug
-
Resolution: Done-Errata
-
Minor
-
OADP 1.3.0
-
False
-
-
False
-
oadp-operator-bundle-container-1.3.1-27
-
ToDo
-
No
-
0
-
0
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
Description
Description of problem:
There is a mismatch in the fs-backup-timeout in OADP and Velero.
Version-Release number of selected component (if applicable):
1.3
How reproducible:
Always
Steps to Reproduce:
Create any basic DPA without fs-backup-timeout arg in configuration.velero:
- apiVersion: oadp.openshift.io/v1alpha1
kind: DataProtectionApplication
metadata:
creationTimestamp: "2023-11-03T15:13:02Z"
generation: 9
name: ts-dpa
namespace: openshift-adp
resourceVersion: "288162"
uid: cc0dbc88-8ff2-449c-9f7a-aa5ac163968e
spec:
backupLocations:
- velero:
credential:
key: cloud
name: cloud-credentials-gcp
default: true
objectStorage:
bucket: oadpbucket244455
prefix: velero
provider: gcp
configuration:
nodeAgent:
enable: true
uploaderType: kopia
velero:
defaultPlugins:
- openshift
- csi
- gcp
snapshotLocations:
- velero:
credential:
key: cloud
name: cloud-credentials-gcp
provider: gcp
status:
conditions:
- lastTransitionTime: "2023-11-03T15:14:56Z"
message: Reconcile complete
reason: Complete
status: "True"
type: Reconciled
$ oc explain dataprotectionapplications.oadp.openshift.io.spec.configuration.velero.args.fs-backup-timeout
KIND: DataProtectionApplication
VERSION: oadp.openshift.io/v1alpha1
FIELD: fs-backup-timeout <integer>
DESCRIPTION:
How long pod volume file system backups/restores should be allowed to run
before timing out. (default 4h0m0s)
Actual results:
$ oc get pods velero-64bc7455c5-htjrx -o yaml | grep fs-backup
- --fs-backup-timeout=1h
Expected results:
Velero pod should have the fs-backup-timeout as 4h.
Additional info:
Attachments
Issue Links
- relates to
-
OADP-3523 [DOC] fs-backup/restic timeout is being changed to 4 hours
-
- Closed
-
- links to
-
RHSA-2024:126995
OpenShift API for Data Protection (OADP) 1.3.1 security and bug fix update
- mentioned on
(1 mentioned on)
