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

DataMover: timeout fails on backup


    • False
    • Hide


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

      Description of problem:

      We run a backup and specified in the DPA:

      dataprotectionapplication.spec.features.dataMover.timeout: 10s

      The backup was in 'InProgress' phase, then after 10s ++ it moved to 'WaitingForPluginOperations' and then to 'Completed'.

      The backup seems to be working even though we specify very low timeout.
      We noticed this issue as a regression in our automation testing as it previously pass.

      I run restore on the same backup, and it fails due to timeout:
      "Timed out awaiting reconciliation of volumesnapshotrestoreList"

      Then I patched the DPA and removed the dataprotectionapplication.spec.features.dataMover.timeout: 10s,
      and run again the restore on the same backup, and it worked.

      So, it seems that the timeout failing with backup, and still working on restore.

      Tested on:
      GCP cloud.

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


      How reproducible:

      Steps to Reproduce:
      1. Create DPA with dataprotectionapplication.spec.features.dataMover.timeout: 10s.
      2. Deploy statefull application namespace.
      3. Run backup on the statefull application namespace.

      Actual results:

      Backup finish successfully.{}

      Expected results:

      Backup shoud fail due to low timeout.

      Additional info:

            wnstb Wes Hayutin
            sbahar Shahaf Bahar
            Shahaf Bahar Shahaf Bahar
            0 Vote for this issue
            9 Start watching this issue