+++ This bug was initially created as a clone of Bug #1765177 +++ 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:
didn't see the issue in recent 4.2 CI job. moving to verified.
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-2019:3869