Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-1834 Datamover backup intermittently reports PartiallyFailed
  3. OADP-2555

[IBM QE-P] Verify Bug OADP-1834 - Datamover backup intermittently reports PartiallyFailed

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • OADP 1.2.6
    • None
    • None
    • None
    • 4
    • False
    • Hide

      None

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

      Description of problem:

      Application backup fails when enabling Datamover.  The backup hangs in WaitingForPluginOperationsstate for a long time before it fails.

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

      1.2.0

      This problem is intermittently and seen with all 1.2 builds. Fails with 63 build also.

       

       

      How reproducible:

      Intermittent

       

      Steps to Reproduce:
      1. Create DPA by enabling datamover, restric secret, volumesnapshotclass
      2. Deploy Mysql application
      3. Take backup

      Actual results:

      Backup fails as PartiallyFailed

       

      Expected results:

      Backup should complete fine

       

      Additional info:

      The volsync pod logs contains below error.

       

      === Starting forget ===

      Fatal: unable to create lock in backend: repository is already locked by PID 46 on volsync-src-vsb-6klc4-rep-src-lc7mf by 1000700000 (UID 1000700000, GID 0)

      lock was created at 2023-05-05 06:18:58 (15m11.351829147s ago)

      storage ID 7b1c3c98

       

       

       

       

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

              Created:
              Updated: