Setting blocker- as this BZ is tracking an E2E test, which isn't critical for the release, but we'll try to get the test merged ASAP nevertheless so we have test coverage for the new feature.
Verified the two e2e tests:- "TestRouterCompressionOperation" and "TestRouterCompressionParsing" ran in the e2e test run from the operator CI logs.
---> latest run:-
-------->From Artifacts ---> "artifacts/" → "e2e-aws-operator/" → "test/" → "build-log.txt"
--- PASS: TestCustomErrorpages (45.14s)
=== RUN TestRouterCompressionParsing
router_compression_test.go:40: deleted ingresscontroller http-compression-1
router_compression_test.go:41: deleted ingresscontroller http-compression-2
router_compression_test.go:42: deleted ingresscontroller http-compression-3
router_compression_test.go:101: failed to update ingress controller, retrying...
router_compression_test.go:53: deleted ingresscontroller http-compression-4
--- PASS: TestRouterCompressionParsing (131.69s)
=== RUN TestRouterCompressionOperation
--- PASS: TestRouterCompressionOperation (59.39s)
ok github.com/openshift/cluster-ingress-operator/test/e2e 2364.646s
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.