Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-1442 OADP-1.2 resourceTimeouts
  3. OADP-1654

[IBM QE-P] Verify Task OADP-1442 - OADP-1.2 resourceTimeouts

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • Quality / Stability / Reliability
    • 4
    • False
    • Hide

      None

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

      Description of problem:

      .spec.configuration.resourceTimeouts

      • The timeout velero waits before timing out
      • Enable OADP to serve large scale deployments that exceed what velero expects by default.

      Upstream bug description: https://github.com/vmware-tanzu/velero/issues/5604

      PR: https://github.com/vmware-tanzu/velero/pull/5926

      A configurable timeout value shared by these timeouts could be created to help prevent further issues. Or it may make more sense to group together related timeouts.

      or

      "A number of unconfigurable timeouts in velero have been updated to give users the ability configure and tune timeouts in velero based on their infrastructure and performance."

       

      emcmulla@redhat.com Can you please provide a DPA example for docs.

      Thanks!

              rh-ee-rkedia Rishika Kedia
              mperetz@redhat.com Maya Peretz
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: