-
Bug
-
Resolution: Done
-
Undefined
-
OADP 1.2.0
-
False
-
-
False
-
oadp-operator-container-1.2.0-33
-
ToDo
-
-
-
0
-
0
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
No
Description of problem:
Created a DPA with non existing VSL secret, DPA got reconciled successfully without any error. DPA should have error when the secret doesn't exists.
Version-Release number of selected component (if applicable):
OADP 1.2 (oadp-operator-bundle-container-1.2.0-36)
How reproducible:
Always
Steps to Reproduce:
1. Create a DPA CR with custom VSL secret. Make sure the VSL secret doesn't existing in OADP namespace.
apiVersion: oadp.openshift.io/v1alpha1 kind: DataProtectionApplication metadata: name: ts-dpa namespace: openshift-adp spec: backupLocations: - velero: credential: key: cloud name: cloud-credentials-gcp default: true objectStorage: bucket: oadpbucket190136 prefix: velero provider: gcp configuration: velero: defaultPlugins: - gcp - openshift - csi snapshotLocations: - velero: config: project: openshift-qe snapshotLocation: us-central1 credential: key: cloud name: test provider: gcp
Actual results:
DPA CR reconciled successfully.
$ oc get dpa ts-dpa -ojsonpath={.status} | jq .
{
"conditions": [
{
"lastTransitionTime": "2023-03-29T06:03:00Z",
"message": "Reconcile complete",
"reason": "Complete",
"status": "True",
"type": "Reconciled"
}
]
}
Expected results:
DPA CR should error out when the secret doesn't exists.
Additional info:
