Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-736

Data mover VSB always fails with volsync 0.5

    XMLWordPrintable

Details

    • False
    • Hide

      None

      Show
      None
    • False
    • oadp-volume-snapshot-mover-container-1.1.0-23
    • Passed
    • No
    • 0
    • 0
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown

    Description

      Description of problem:

      Volsync 0.5 handles the CR status differently than 0.3 and 0.4. Due to these changes, VSB always fails while updating its status: https://github.com/konveyor/volume-snapshot-mover/blob/master/controllers/replicationsource.go#L101 

       

       

      How reproducible:

      100%

       

      Steps to Reproduce:
      1. Run Volsync controller on 0.5 
      2. Create a data mover backup
      3. check vsb status.phase when available 

      Actual results:

      vsb.Status.Phase is always failed

      Expected results:

      vsb.Status.Phase is inProgress or Completed

      Attachments

        Activity

          People

            emcmulla@redhat.com Emily McMullan
            rhn-engineering-dymurray Dylan Murray
            Maya Peretz Maya Peretz
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: