Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-50516

[release-4.17] Increase waitForFallbackDegradedConditionTimeout of test e2e-sno-disruptive

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • None
    • 4.14.z, 4.15.z, 4.17.z, 4.16.z, 4.18.0, 4.19.0
    • kube-apiserver
    • None
    • Moderate
    • None
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • Done

      This is a clone of issue OCPBUGS-50479. The following is the description of the original issue:
      —
      Description of problem:

      The KAS-O has a job that tests the fallback scenario on the SNO platform. That job had been failing permanently for a very long time.

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

      4.19

      How reproducible:

      always

      Steps to Reproduce:

         test/e2e-sno-disruptive/sno_disruptive_test.go always runs into failure.

      Actual results:

          test/e2e-sno-disruptive/sno_disruptive_test.go always runs into failure.

      Expected results:

           test/e2e-sno-disruptive/sno_disruptive_test.go should run passed.

      Additional info:

              wk2019 Ke Wang
              openshift-crt-jira-prow OpenShift Prow Bot
              Ke Wang Ke Wang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: