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
If the default router is not exposed by a load balancer service on ovirt we would have to skip this test.
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
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