HTTPRouteListenerHostnameMatching Conformance Test Fails

[danehans]

The HTTPRouteListenerHostnameMatching conformance test is failing.

Test Logs:

http.go:159: Response expectation failed, not ready yet: expected status code to be 200, got 404
Sending Request:
< GET / HTTP/1.1
< Host: multiple.prefixes.foo.com
< User-Agent: Go-http-client/1.1
< Accept-Encoding: gzip
<
<

Received Response:
< HTTP/1.1 404 Not Found
< Date: Tue, 27 Sep 2022 17:42:46 GMT
< Server: envoy
< Content-Length: 0
<
<

=== CONT  TestGatewayAPIConformance/HTTPRouteListenerHostnameMatching/3_request_to_boo.bar.com/_should_go_to_infra-backend-v3
    http.go:159: Response expectation failed, not ready yet: expected status code to be 200, got 404
...
--- FAIL: TestGatewayAPIConformance (57.92s)
    --- FAIL: TestGatewayAPIConformance/HTTPRouteListenerHostnameMatching (6.92s)
        --- PASS: TestGatewayAPIConformance/HTTPRouteListenerHostnameMatching/6_request_to_foo.com/_should_go_to_ (0.01s)
        --- PASS: TestGatewayAPIConformance/HTTPRouteListenerHostnameMatching/7_request_to_no.matching.host/_should_go_to_ (0.01s)
        --- FAIL: TestGatewayAPIConformance/HTTPRouteListenerHostnameMatching/4_request_to_multiple.prefixes.bar.com/_should_go_to_infra-backend-v3 (30.00s)
        --- FAIL: TestGatewayAPIConformance/HTTPRouteListenerHostnameMatching/0_request_to_bar.com/_should_go_to_infra-backend-v1 (30.00s)
        --- FAIL: TestGatewayAPIConformance/HTTPRouteListenerHostnameMatching/1_request_to_foo.bar.com/_should_go_to_infra-backend-v2 (30.00s)
        --- FAIL: TestGatewayAPIConformance/HTTPRouteListenerHostnameMatching/2_request_to_baz.bar.com/_should_go_to_infra-backend-v3 (30.00s)
        --- FAIL: TestGatewayAPIConformance/HTTPRouteListenerHostnameMatching/3_request_to_boo.bar.com/_should_go_to_infra-backend-v3 (30.00s)
        --- FAIL: TestGatewayAPIConformance/HTTPRouteListenerHostnameMatching/5_request_to_multiple.prefixes.foo.com/_should_go_to_infra-backend-v3 (30.00s)
FAIL

EG Logs:

2022-09-27T17:37:24.428Z	INFO	cache/logrwrapper.go:24	handling v3 xDS resource request, version_info 281, response_nonce 1233, nodeID envoy-57688c956d-586r8, node_version v1.23.1, resource_names [], type_url type.googleapis.com/envoy.config.listener.v3.Listener, errorCode 13, errorMessage Error adding/updating listener(s) listener_gateway-conformance-infra-httproute-listener-hostname-matching-listener-1_10080: error adding listener: 'listener_gateway-conformance-infra-httproute-listener-hostname-matching-listener-1_10080' has duplicate address '0.0.0.0:10080' as existing listener
listener_gateway-conformance-infra-httproute-listener-hostname-matching-listener-2_10081: error adding listener: 'listener_gateway-conformance-infra-httproute-listener-hostname-matching-listener-2_10081' has duplicate address '0.0.0.0:10081' as existing listener
listener_gateway-conformance-infra-httproute-listener-hostname-matching-listener-3_10082: error adding listener: 'listener_gateway-conformance-infra-httproute-listener-hostname-matching-listener-3_10082' has duplicate address '0.0.0.0:10082' as existing listener
	{"runner": "xds-server"}

Verify the use of ValidUniqueListenerPorts in the conformance test setup works for test case Gateways and not just base manifest gateways.

xref: https://kubernetes.slack.com/archives/CR0H13KGA/p1664300797476109

This issue may be resolved by #404

[skriss]

It looks like #441 is also at play here, the Service name is too long to be valid.

[Alice-Lilith]

Seems like the main issue still blocking this one is in the test yaml there are multiple listeners that all use the same port