Bug 2008201 - openstack-az job is failing on haproxy idle test
Summary: openstack-az job is failing on haproxy idle test
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.9
Hardware: All
OS: All
low
low
Target Milestone: ---
: 4.10.0
Assignee: Emilien Macchi
QA Contact: Emilien Macchi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-27 15:03 UTC by Stephen Benjamin
Modified: 2022-03-12 04:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-12 04:38:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift release pull 22271 0 None open Bug 2008201: openstack-az: skip one recurring failing test 2021-09-27 16:43:36 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-12 04:38:55 UTC

Description Stephen Benjamin 2021-09-27 15:03:04 UTC
periodic-ci-openshift-release-master-nightly-4.10-e2e-openstack-az is failing the following test in CI:

[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 [Skipped:Disconnected] [Suite:openshift/conformance/parallel/minimal]

Error:

--> Deploying template "e2e-test-router-idling-hc9m4/" for "/tmp/fixture-testdata-dir554217212/test/extended/testdata/router/router-idle.yaml" to project e2e-test-router-idling-hc9m4

--> Creating resources ...
    route.route.openshift.io "idle-test" created
    service "idle-test" created
    deployment.apps "idle-test" created
--> Success
    Access your application via route 'idle-test-e2e-test-router-idling-hc9m4.apps.dvh326g1-b4426.shiftstack.devcluster.openshift.com' 
    Run 'oc status' to view your app.
STEP: Waiting for pods to be running
Sep 14 21:06:28.606: INFO: Waiting for 1 pods in namespace e2e-test-router-idling-hc9m4
Sep 14 21:06:30.639: INFO: All expected pods in namespace e2e-test-router-idling-hc9m4 are running
STEP: Getting a 200 status code when accessing the route
Sep 14 21:07:02.675: INFO: GET#1 "http://idle-test-e2e-test-router-idling-hc9m4.apps.dvh326g1-b4426.shiftstack.devcluster.openshift.com" error=Get "http://idle-test-e2e-test-router-idling-hc9m4.apps.dvh326g1-b4426.shiftstack.devcluster.openshift.com": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Sep 14 21:07:33.675: INFO: GET#2 "http://idle-test-e2e-test-router-idling-hc9m4.apps.dvh326g1-b4426.shiftstack.devcluster.openshift.com" error=Get "http://idle-test-e2e-test-router-idling-hc9m4.apps.dvh326g1-b4426.shiftstack.devcluster.openshift.com": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Sep 14 21:08:04.675: INFO: GET#3 "http://idle-test-e2e-test-router-idling-hc9m4.apps.dvh326g1-b4426.shiftstack.devcluster.openshift.com" error=Get "http://idle-test-e2e-test-router-idling-hc9m4.apps.dvh326g1-b4426.shiftstack.devcluster.openshift.com": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Sep 14 21:08:35.674: INFO: GET#4 "http://idle-test-e2e-test-router-idling-hc9m4.apps.dvh326g1-b4426.shiftstack.devcluster.openshift.com" error=Get "http://idle-test-e2e-test-router-idling-hc9m4.apps.dvh326g1-b4426.shiftstack.devcluster.openshift.com": dial tcp 172.16.0.7:80: i/o timeout (Client.Timeout exceeded while awaiting headers)


Example job:
https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.10-e2e-openstack-az/1437862404779151360

Comment 3 Emilien Macchi 2021-11-10 11:16:31 UTC
the job is now passing:
https://prow.ci.openshift.org/job-history/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.10-e2e-openstack-az

And we now skip the test mentioned in this BZ.
I'll mark as verified.

Comment 4 ShiftStack Bugwatcher 2021-11-25 16:12:34 UTC
Removing the Triaged keyword because:

* the QE automation assessment (flag qe_test_coverage) is missing

Comment 7 errata-xmlrpc 2022-03-12 04:38:40 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.10.3 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-2022:0056


Note You need to log in before you can comment on or make changes to this bug.