Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1765181

Summary:	[4.1] Many router e2e tests are flaky due to a buggy wait script
Product:	OpenShift Container Platform	Reporter:	Dan Mace <dmace>
Component:	Networking	Assignee:	Dan Mace <dmace>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aos-bugs, hongli
Version:	4.1.z
Target Milestone:	---
Target Release:	4.1.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1765177	Environment:
Last Closed:	2020-01-17 17:37:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1765177
Bug Blocks:

Description Dan Mace 2019-10-24 13:20:19 UTC

+++ 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:

Comment 1 Dan Mace 2020-01-17 17:37:38 UTC

There's some additional work to get this back ported — will proceed with best effort, but due to age, lack of impact, and low severity, we're going to close the bug.