Description

If the DataProtectionApplication backupLocations has an existing named backupLocation:

Adding a second backupLocation with the same name is not rejected as invalid state. This is not allowed because the name is used to create BackupStorageLocation objects. Duplicate named objects are not allowed by Kubernetes.

Impact: 

The OADP Operator continually updates the BackupStorageLocation with the differing values continually.

This causes Backup and Restore failure due to Velero fails to read the Secret credentials of the BackupStorageLocation if the provider types are different (aws, azure, gcp).

Workarounds:

Remove the offending duplicate DPA backupLocations

External Info:

Fusion Item 57948