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

Pods with volumes for fsbackup/restic chosen by annotation aren't restored

XMLWordPrintable

    • False
    • Hide

      None

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

      Description of problem:

      The OADP openshift plugin has code to skip pod restore if owned by another resource (Deployment, etc) if it doesn't have pod hooks or volumes to back up via restic. This works fine when selecting volumes for restic via the default-volumes-to-fs-backup flag, but it does not currently work properly when not defaulting to  fs backup and individually selecting volumes via the "backup.velero.io/backup-volumes" annotation

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

       

      How reproducible:

      Always

      Steps to Reproduce:
      1. OADP installed, not defaulting volumes to fs backup
      2. Create a namespace with a deployment with a mounted PVC
      3. Set the "backup.velero.io/backup-volumes" annotation on the pod (name is from pod.spec.volumes[].name, not PVC name)
      4. Back up the namespace
      5. Delete the namespace
      6. Restore the namespace

      Actual results:

      restic restore doesn't restore the volume contents because the plugin discards the pod.

      Expected results:

      Application was restored

      Additional info:

            sseago Scott Seago
            sseago Scott Seago
            Prasad Joshi Prasad Joshi
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: