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

ResticRepository can become stale after BSL bucket changes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Critical Critical
    • OADP 1.2.5
    • OADP 1.1.0
    • velero
    • False
    • Hide

      None

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

      Description of problem:

      See https://github.com/vmware-tanzu/velero/issues/5226

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

       

      How reproducible:

       

      Steps to Reproduce:

      create BackupStorageLocation to point to bucketABC
      Create backup A with defaultVolumeToRestic: true

      update BackupStorageLocation to point to bucketDEF keeping the same BSL name
      Create backup B with defaultVolumeToRestic: true

      Object manifests for backup B are in bucketDEF
      Restic backup data for backup B are in bucketABC

      What did you expect to happen:
      Object manifests, and restic backup data for backup B are in bucketDEF

      Actual results:

       

      Expected results:

       

      Additional info:

      Workaround include manually deleting ResticRepository before making BSL changes.
      Upstream PR https://github.com/vmware-tanzu/velero/pull/5227

              tkaovila@redhat.com Tiger Kaovilai
              tkaovila@redhat.com Tiger Kaovilai
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: