-
Sub-task
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
ToDo
-
-
-
0
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
Description of problem:
DPA doesnt report any error if the provider of a Volume Snapshot Location spec is incorrect. This doesnt match with the behaviour of BSL, It reports error immediately.
Version-Release number of selected component (if applicable):
1.4.1
How reproducible:
Always
Steps to Reproduce:
1. Deploy OADP
2. Create DPA with VSL spec and provider = <any incorrect value>
Actual results:
DPA reconciles successfully
Expected results:
DPA should throw an error, asking for a valid provider value.
Additional info:
DPA:
apiVersion: v1
items:
- apiVersion: oadp.openshift.io/v1alpha1
kind: DataProtectionApplication
metadata:
creationTimestamp: "2024-10-13T13:24:17Z"
generation: 22
name: ts-dpa
namespace: openshift-adp
resourceVersion: "241758"
uid: 27ca2e75-fb5f-4c96-8a3c-00edf716cae5
spec:
backupLocations:
- velero:
config:
resourceGroup: oadp-98691-ghtqs-rg
storageAccount: oadp98691ghtqs
storageAccountKeyEnvVar: AZURE_STORAGE_ACCOUNT_ACCESS_KEY
subscriptionId: 53b8f551-f0fc-4bea-8cba-6d1fefd54c8a
credential:
key: cloud
name: cloud-credentials
default: true
objectStorage:
bucket: oadp98691ghtqs
prefix: velero
provider: azure
configuration:
nodeAgent:
enable: true
uploaderType: kopia
velero:
defaultPlugins:
- openshift
- azure
snapshotLocations:
- velero:
config:
resourceGroup: oadp-98691-ghtqs-rg
subscriptionId: 53b8f551-f0fc-4bea-8cba-6d1fefd54c8a
credential:
key: cloud
name: cloud-credentials
provider: jingalalahu
status:
conditions:
- lastTransitionTime: "2024-10-13T19:28:07Z"
message: Reconcile complete
reason: Complete
status: "True"
type: Reconciled
