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

Bug 1933114

Summary:	[sig-network-edge][Conformance][Area:Networking][Feature:Router] The HAProxy router should be able to connect to a service that is idled because a GET on the route will unidle it [Suite:openshift/conformance/parallel/minimal]
Product:	OpenShift Container Platform	Reporter:	Oleg Bulatov <obulatov>
Component:	Networking	Assignee:	Andrew McDermott <amcdermo>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	amcdermo, aos-bugs, bperkins
Version:	4.8
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-27 22:48:26 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:
Bug Depends On:
Bug Blocks:	1941574

Description Oleg Bulatov 2021-02-25 17:27:10 UTC

Description of problem:

The test `The HAProxy router should be able to connect to a service that is idled because a GET on the route will unidle it` often fails on the job periodic-ci-openshift-release-master-ocp-4.8-e2e-ovirt.

The error usually says `connect: no route to host`.

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

4.8

How reproducible:

Often

Steps to Reproduce:
1. run the CI job

Additional info:

Failing job:

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.8-e2e-ovirt/1364736565154156544

Test output:

...
Feb 25 01:46:11.767: INFO: GET#718 "http://idle-test-e2e-test-router-idling-dbnc5.apps.ovirt19.gcp.devcluster.openshift.com" error=Get "http://idle-test-e2e-test-router-idling-dbnc5.apps.ovirt19.gcp.devcluster.openshift.com": dial tcp 169.46.38.142:80: connect: no route to host
Feb 25 01:46:12.770: INFO: GET#719 "http://idle-test-e2e-test-router-idling-dbnc5.apps.ovirt19.gcp.devcluster.openshift.com" error=Get "http://idle-test-e2e-test-router-idling-dbnc5.apps.ovirt19.gcp.devcluster.openshift.com": dial tcp 169.46.38.142:80: connect: no route to host
Feb 25 01:46:13.772: INFO: GET#720 "http://idle-test-e2e-test-router-idling-dbnc5.apps.ovirt19.gcp.devcluster.openshift.com" error=Get "http://idle-test-e2e-test-router-idling-dbnc5.apps.ovirt19.gcp.devcluster.openshift.com": dial tcp 169.46.38.142:80: connect: no route to host
Feb 25 01:46:14.767: INFO: GET#721 "http://idle-test-e2e-test-router-idling-dbnc5.apps.ovirt19.gcp.devcluster.openshift.com" error=Get "http://idle-test-e2e-test-router-idling-dbnc5.apps.ovirt19.gcp.devcluster.openshift.com": dial tcp 169.46.38.142:80: connect: no route to host

Comment 1 Andrew McDermott 2021-02-25 18:24:59 UTC

If the default router is not exposed by a load balancer service on ovirt we would have to skip this test.

Comment 3 Hongan Li 2021-03-15 03:41:36 UTC

verified and passed, the test is skipped on virt platform CI job. 

see https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.8-e2e-ovirt/1371159348029427712

Comment 6 errata-xmlrpc 2021-07-27 22:48:26 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438