-
Bug
-
Resolution: Unresolved
-
Normal
-
OADP 1.3.0
-
False
-
-
False
-
ToDo
-
No
-
-
-
0
-
0
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
Description of problem:
Created a DPA without enabling the nodeAgent config. Backup was stuck in waitingForPluginOperations phase until it hits timeout error. When I tested the same thing with FileSytemBackup, backup failed with error daemonset pod not found. This validation is missing in case of built-in Datamover.
Version-Release number of selected component (if applicable):
OADP 1.3.0
How reproducible:
Always
Steps to Reproduce:
1. Create a DPA with CSI enabled.
2. Deploy a stateful application
3. Create a backup with SnapshotMoveData flag set as true
apiVersion: velero.io/v1 kind: Backup metadata: name: test-backup3 labels: velero.io/storage-location: default namespace: openshift-adp spec: includedNamespaces: - ocp-mysql storageLocation: ts-dpa-1 snapshotMoveData: true
Actual results:
Backup gets stuck in WaitingForPluginsOperation phase until it hits timeout error.
$ oc get backup test-backup3 -o yaml apiVersion: velero.io/v1 kind: Backup metadata: annotations: velero.io/resource-timeout: 10m0s velero.io/source-cluster-k8s-gitversion: v1.27.6+98158f9 velero.io/source-cluster-k8s-major-version: "1" velero.io/source-cluster-k8s-minor-version: "27" creationTimestamp: "2023-10-18T13:21:08Z" generation: 5 labels: velero.io/storage-location: ts-dpa-1 name: test-backup3 namespace: openshift-adp resourceVersion: "212060" uid: 1f252fb5-eb00-4efb-b576-12c6f7169a92 spec: csiSnapshotTimeout: 10m0s defaultVolumesToFsBackup: false includedNamespaces: - ocp-mysql itemOperationTimeout: 4h0m0s snapshotMoveData: true storageLocation: ts-dpa-1 ttl: 720h0m0s status: backupItemOperationsAttempted: 2 expiration: "2023-11-17T13:21:08Z" formatVersion: 1.1.0 phase: WaitingForPluginOperations progress: itemsBackedUp: 31 totalItems: 31 startTimestamp: "2023-10-18T13:21:09Z" version: 1
Expected results:
Backup should get immediately failed in case nodeAgent pods are not running.
Additional info:
