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

kubevirt vm's using filesystemOverhead fail in backup/restore due to volume size mismatch

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • oadp-operator-bundle-container-1.2.2-10
    • ToDo
    • Critical
    • 10
    • 0
    • Very Likely
    • 0
    • Customer Escalated, Customer Facing
    • None
    • Unset
    • Unknown
    • No

      Description of problem:

      The context of this issue is for datamover enabled backup and restores only.

      filesystemOverhead: https://kubevirt.io/cdi-api-reference/v1.27.0/definitions.html#_v1beta1_filesystemoverhead

      ATM oadp is not taking into account the additional size of the pv with the filesystemOverhead setting.  The backup and restore cloned pv's fail to bind and oadp fails.

      This can also occur outside of kubevirt in a pod volume backup if the restore size is greater than the PVC storage request.  As documented here: https://github.com/kubernetes-csi/external-provisioner/issues/727

       

      If a user is hitting this issue they may see errors like:
      failed for volume "pvc-1f7ee50e-1e12-4d00-960e-c3a31a2e5595" : rpc error: code = Unavailable desc = Failed to mount volume 702845133932259600: not a directory
      29s Warning FailedMount pod/vsb-c89c8-pod
       

      The associated customer case is here:

      https://access.redhat.com/support/cases/#/case/03544060

       

       

       

       

       

       

              spampatt@redhat.com Shubham Pampattiwar
              wnstb Wes Hayutin
              Shubham Pampattiwar, Wes Hayutin
              Amos Mastbaum Amos Mastbaum
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: