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

Bug 1703885

Summary:	[ci] [aws] Router test fails with "error 7" while trying to reach backend
Product:	OpenShift Container Platform	Reporter:	Clayton Coleman <ccoleman>
Component:	Networking	Assignee:	Dan Mace <dmace>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	low	CC:	aos-bugs, nagrawal
Version:	4.1.0
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-16 06:28:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Clayton Coleman 2019-04-29 02:09:37 UTC

The router test is failing with "error 7" which is usually connection refused or no route to host errors and is usually symptomatic of networking failures. 

Needs investigation and potentially transferring to network team.

https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.1/329#openshift-tests-conformanceareanetworkingfeaturerouter-the-haproxy-router-should-run-even-if-it-has-no-access-to-update-status-suiteopenshiftconformanceparallelminimal

[Conformance][Area:Networking][Feature:Router] The HAProxy router should run even if it has no access to update status [Suite:openshift/conformance/parallel/minimal] 3m49s


fail [github.com/openshift/origin/test/extended/router/unprivileged.go:87]: Expected error:
    <*errors.errorString | 0xc0030e8020>: {
        s: "last response from server was not 200:\n",
    }
    last response from server was not 200:
    
not to have occurred

Comment 2 Dan Mace 2019-08-14 20:38:52 UTC

I'm lowering the severity of this given the absence of evidence of an issue with flakiness on master. If there's a CI search that shows this issue has become significant to blocking PRs, we can reprioritize. For now, I don't see this as a release blocker.

Comment 3 Miciah Dashiel Butler Masters 2019-08-15 21:42:48 UTC

https://github.com/openshift/origin/pull/23614 may not fix the failures but may make them easier to diagnose.

Comment 5 Hongan Li 2019-08-20 08:05:11 UTC

The PR is for diagnosis but since it was merged and didn't see the issue recently so I moving the BZ to verified for now.

Will keep an eye on ci job and reopen if it occurs again.

Comment 6 errata-xmlrpc 2019-10-16 06:28:21 UTC

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