Add tests to the cluster-ingress-operator in-repo e2e suite to test the timeout variables added in https://issues.redhat.com/browse/NE-412
The test case appears to execute successfully in the latest "4.9.0-0.nightly-2021-08-29-010334" release. ---- WATCH_NAMESPACE=openshift-ingress-operator go test -v -tags e2e -count 1 -run TestHAProxyTimeouts . I0830 10:51:39.141407 39543 request.go:668] Waited for 1.048296293s due to client-side throttling, not priority and fairness, request: GET:https://api.aiyengar49te.qe.devcluster.openshift.com:6443/apis/apiextensions.k8s.io/v1?timeout=32s === RUN TestHAProxyTimeouts haproxy_timeouts_test.go:177: deleted ingresscontroller haproxy-timeout --- PASS: TestHAProxyTimeouts (48.86s) === RUN TestHAProxyTimeoutsRejection haproxy_timeouts_test.go:317: deleted ingresscontroller haproxy-timeout-rejection --- PASS: TestHAProxyTimeoutsRejection (44.76s) PASS ok github.com/openshift/cluster-ingress-operator/test/e2e 98.743s ----
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.9.0 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:3759