Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-4617 Upstream Fix: Velero didn't retry on failed Restore CR status update, causing the CR to remain stuck in "InProgress"
  3. OADP-4619

[IBM QE-P] Verify Feature Request OADP-4617 - Upstream Fix: Velero didn't retry on failed Restore CR status update, causing the CR to remain stuck in "InProgress"

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • OADP 1.5.0
    • None
    • None
    • None
    • 4
    • False
    • Hide

      None

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

      Tracking upstream fix of OADP-3227 that we currently carry in 1.3 and 1.4 via requeueing
      Upstream Issue: https://github.com/vmware-tanzu/velero/issues/7207
      Design: https://github.com/vmware-tanzu/velero/pull/8063/
      Implementation: TBD
      -

      Proposed title of this feature request
      -

      What is the nature and description of the request?
      -

      Why does the customer need this? (List the business requirements here)
      -

      Optional: List affected component/s.

              sgarudi Sonia Garudi
              akarol@redhat.com Aziza Karol
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: