Routes are not working on the newly revived e2e-aws-proxy job, presumably because the ELB domain is not no-proxied by default. Eg, see https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.6-e2e-aws-proxy/1308949438701506560
To clarify this BZ, router e2e tests that curl the ELB url directly with host headers to test a sample route/ingress are not working for the e2e-aws-proxy job, which focuses on cluster proxy egress functionality. [sig-network][Feature:Router] The HAProxy router should respond with 503 to unrecognized hosts [sig-network][Feature:Router] The HAProxy router should serve routes that were created from an ingress [sig-network][Feature:Router] The HAProxy router should support reencrypt to services backed by a serving certificate automatically Additionally, see https://testgrid.k8s.io/redhat-openshift-ocp-release-4.6-informing#periodic-ci-openshift-release-master-ocp-4.6-e2e-aws-proxy Note that the console operator status test has passed a few times, so to say that routes flat out don't work as is on the e2e-aws-proxy job is naive.
See skipped tests here https://github.com/openshift/release/pull/12233/files
As part of fixing this, you should drop at least these skips [1] and show that the test-cases pass in proxy CI. [1]: https://github.com/openshift/release/blob/4c9dd40104656afb73e609e3c3d39c0c86bc57b4/ci-operator/step-registry/openshift/e2e/aws/proxy/openshift-e2e-aws-proxy-workflow.yaml#L18-L21
Also maybe 'Image append should create images by appending them', since that also seems to be an issue with the test pod not knowing that it should use the proxy.
I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.
Proxy CI is not feeling well again, so I cannot test my proposed fix at the moment. The team has decided that is appropriate to keep working on proxy CI during the bug fix phase of 4.7, just with lower priority than other bugs.
Bumping the priority so we address the skipped tests. We will be re-enabling http/2 tests (http/2, gRPC and h2spec) and they may/will also fail with proxy jobs.
Going to crank the verbosity of the failing tests and churn them through proxy CI to try and figure out the issue here (and if its something we should actually fix).
Tests that fall under NE responsibility to unskip: Managed cluster should should expose cluster services outside the cluster\| The HAProxy router should respond with 503 to unrecognized hosts\| The HAProxy router should serve routes that were created from an ingress\| The HAProxy router should set Forwarded headers appropriately\| The HAProxy router should support reencrypt to services backed by a serving certificate automatically\|
*** Bug 1882853 has been marked as a duplicate of this bug. ***