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

ReloadInterval E2E test has both incorrect verifications and a race condition

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 4.12.z
    • 4.12
    • Networking / router
    • None
    • Important
    • None
    • 3
    • Sprint 226
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      The TestReloadInterval E2E test has completely wrong validations in which the min value should be 1s, not 5s.
      
      But there is a race condition which allow these tests to sometimes pass due to the last test condition.
      
      Therefore, failures in CI are actually correct, and successes are wrong based on the E2E conditions.

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

      4.12

      How reproducible:

      50%

      Steps to Reproduce:

      1.Run TestReloadInterval E2E test (make test-e2e TEST=TestReloadInterval)
      

      Actual results:

      Sometimes fails on 5us test case:
      
      reloadinterval_test.go:106: router deployment not updated with RELOAD_INTERVAL=5s: timed out waiting for the condition

      Expected results:

      Should pass E2E

      Additional info:

       

       

       

       

            gspence@redhat.com Grant Spence
            gspence@redhat.com Grant Spence
            Shudi Li Shudi Li
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: