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

[DataMover] Timeout configuration is not relevant and should be removed

XMLWordPrintable

    • False
    • Hide

      None

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

      Description of problem:

      The configuration:

      dataprotectionapplications.oadp.openshift.io.spec.features.dataMover.timeout
      Was used in 1.1 performance improvements, and it is not relevant anymore for 1.2.

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

      oadp-operator-bundle-container-1.2.0-79

      How reproducible:

       

      Steps to Reproduce:
      https://polarion.engineering.redhat.com/polarion/#/project/OADP/workitem?id=OADP-226
      https://polarion.engineering.redhat.com/polarion/#/project/OADP/workitem?id=OADP-225

      Actual results:

      Already discussed:

      https://issues.redhat.com/browse/OADP-1672

      Expected results:

      https://issues.redhat.com/browse/OADP-1672

      Additional info:

      https://issues.redhat.com/browse/OADP-1672

       

      HOW TO TEST:

      oc explain dataprotectionapplications.oadp.openshift.io.spec.features.dataMover
      result: timeout field is not present

        1.
        		 [RedHat QE] Verify Bug OADP-2045 - [DataMover] Timeout configuration is not relevant and should be removed Sub-task New Undefined Wes Hayutin
        2.
        		 [IBM QE-P] Verify Bug OADP-2045 - [DataMover] Timeout configuration is not relevant and should be removed Sub-task New Undefined Rishika Kedia
        3.
        		 [IBM QE-Z] Verify Bug OADP-2045 - [DataMover] Timeout configuration is not relevant and should be removed Sub-task New Undefined Rishika Kedia

            wnstb Wes Hayutin
            sbahar Shahaf Bahar
            Shahaf Bahar Shahaf Bahar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: