Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-4308 DataUpload/DataDownload is getting canceled when using ceph storage class
  3. OADP-4333

[IBM QE-Z] Verify Bug OADP-4308 - DataUpload/DataDownload is getting canceled when using ceph storage class

XMLWordPrintable

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

      None

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

      Description of problem:

      Currently datamover backup/restores are partially failing due to the dataupload/download getting cancelled in case of ceph storage class.  

      We observed that the backups are getting failed more frequently with ceph-RBD storageclass. In case of ceph-fs the restore is failing more frequently. 

      Attached error below:- 

       message: 'found a dataupload openshift-adp/backup20-llp79 with expose error: Pod
        is unschedulable: 0/6 nodes are available: pod has unbound immediate PersistentVolumeClaims.
        preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling...
        mark it as cancel'

       

       

      Version-Release number of selected component (if applicable):
      OADP 1.4.0 -6 
      OCP 4.14 & OCP 4.15 

       

      How reproducible:
      Always (100% in case of IBM Z platform)

       

      Steps to Reproduce:
      1. Create a DPA with CSI and nodeAgent enabled.
      2. Deploy a stateful application 
      3. Trigger dataMover backup
      4. In case backup didn't fail, delete app namespace and trigger restore. 

       

      Actual results:
      DataUpload/Download is getting cancelled with below error causing backup/restore to partially fail.

       message: 'found a dataupload openshift-adp/backup20-llp79 with expose error: Pod
        is unschedulable: 0/6 nodes are available: pod has unbound immediate PersistentVolumeClaims.
        preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling...
        mark it as cancel'

       

      Expected results:

      Dataupload/datadownload should be successful. 

       

      Additional info:

              uprasad@redhat.com Ukthi Prasad
              akarol@redhat.com Aziza Karol
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: