Description of problem: Many router tests use waitForRouterOKResponseExec() to wait for test route connectivity. However, due to a bug in the check script, if the underlying curl command times out once during checks, the waitForRouterOKResponseExec() function will always time out even if the target route becomes responsive. If the curl command itself never times out, the function works properly. Other bugs which are likely explained by this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1753472 https://bugzilla.redhat.com/show_bug.cgi?id=1753734 https://bugzilla.redhat.com/show_bug.cgi?id=1762653 https://bugzilla.redhat.com/show_bug.cgi?id=1762149 https://bugzilla.redhat.com/show_bug.cgi?id=1764076 https://bugzilla.redhat.com/show_bug.cgi?id=1764079 https://bugzilla.redhat.com/show_bug.cgi?id=1764081 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Also depends on https://github.com/openshift/origin/pull/24028
monitoring the e2e test for some days to ensure the fix works.
In the past two days since the fix merged I'm no longer seeing evidence of any of the flakes associated with this bug. https://ci-search-ci-search-next.svc.ci.openshift.org/?search=failed%3A.*override+the+route+host+for+overridden+domains&maxAge=48h&context=2&type=all https://ci-search-ci-search-next.svc.ci.openshift.org/?search=failed%3A.*router+should+serve+a+route+that+points+to+two+services&maxAge=48h&context=2&type=all https://ci-search-ci-search-next.svc.ci.openshift.org/?search=failed%3A.*router+should+serve+the+correct+routes+when+scoped+to+a+single+namespace&maxAge=48h&context=2&type=all https://ci-search-ci-search-next.svc.ci.openshift.org/?search=failed%3A.*router+should+run+even+if+it+has+no+access+to+update+status+&maxAge=48h&context=2&type=all I recommend we declare this fixed and open new bugs as necessary.
the related bugs have been verified so moving this to verified too.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062