Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-6459 Adding a backupLocation to DPA with an existing backupLcation name is not rejected
  3. OADP-6532

[IBM QE-P] Verify Bug OADP-6459 - Adding a backupLocation to DPA with an existing backupLcation name is not rejected

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • OADP 1.5.1
    • None
    • None
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown

      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

              anayek Aniruddha Nayek
              akarol@redhat.com Aziza Karol
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: