Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-2175 Make use of restic secret to pass datamover retain policy instead of datamover config map
  3. OADP-2210

[IBM QE-P] Verify Bug OADP-2175 - Make use of restic secret to pass datamover retain policy instead of datamover config map

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • 4
    • False
    • Hide

      None

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

      Description of problem:

      In OADP 1.2, we used datamover config map in order to pass the values of retain policy from DPA CR to replicationSource CR, but this meant that we had to assign volume options as well due to the nature of changes that went in the volume options feature PR. (Shared config map of volume options and retain policy)

      Version-Release number of selected component (if applicable):

       

      How reproducible:

      Everytime

      Steps to Reproduce:
      1. Setup retain policy on DPA without volume options
      2. Retain policy does not get cascaded to replicationSource from DPA

      Actual results:

      Retain policy not set on replicationSource

      Expected results:

      Retain policy to be set on replicationSource

      Additional info:

              sgarudi Sonia Garudi
              akarol@redhat.com Aziza Karol
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: