-
Notifications
You must be signed in to change notification settings - Fork 714
HTTPRouteMatching Conformance Test Fails #436
Copy link
Copy link
Closed
Labels
area/ciCI and build related issuesCI and build related issuesarea/conformanceGateway API Conformance Related IssuesGateway API Conformance Related Issueshelp wantedExtra attention is neededExtra attention is neededkind/bugSomething isn't workingSomething isn't working
Milestone
Description
The HTTPRouteMatching conformance test is failing.
Test Logs:
...
http.go:159: Response expectation failed, not ready yet: expected pod name to start with infra-backend-v2, got infra-backend-v1-c565b8f4d-frqtl
Received Response:
< HTTP/1.1 200 OK
< Content-Length: 492
< Content-Type: application/json
< Date: Tue, 27 Sep 2022 19:02:49 GMT
< Server: envoy
< X-Content-Type-Options: nosniff
< X-Envoy-Upstream-Service-Time: 0
<
< {
< "path": "/",
< "host": "127.0.0.1:80",
< "method": "GET",
< "proto": "HTTP/1.1",
< "headers": {
< "Accept-Encoding": [
< "gzip"
< ],
< "User-Agent": [
< "Go-http-client/1.1"
< ],
< "Version": [
< "two"
< ],
< "X-Envoy-Expected-Rq-Timeout-Ms": [
< "15000"
< ],
< "X-Forwarded-Proto": [
< "http"
< ],
< "X-Request-Id": [
< "18591a0f-5c17-4003-8c5e-97abd26d8d5f"
< ]
< },
< "namespace": "gateway-conformance-infra",
< "ingress": "",
< "service": "",
< "pod": "infra-backend-v1-c565b8f4d-frqtl"
< }
=== CONT TestGatewayAPIConformance/HTTPRouteMatching/5_request_to_/_with_headers_should_go_to_infra-backend-v2
http.go:159: Response expectation failed, not ready yet: expected pod name to start with infra-backend-v2, got infra-backend-v1-c565b8f4d-frqtl
=== CONT TestGatewayAPIConformance/HTTPRouteMatching/4_request_to_/v2/example_should_go_to_infra-backend-v2
http.go:140: timeout while waiting after 30 attempts, 0/3 sucessess
...
--- FAIL: TestGatewayAPIConformance (53.18s)
--- FAIL: TestGatewayAPIConformance/HTTPRouteMatching (2.06s)
--- PASS: TestGatewayAPIConformance/HTTPRouteMatching/1_request_to_/example_should_go_to_infra-backend-v1 (0.01s)
--- PASS: TestGatewayAPIConformance/HTTPRouteMatching/0_request_to_/_should_go_to_infra-backend-v1 (0.01s)
--- PASS: TestGatewayAPIConformance/HTTPRouteMatching/2_request_to_/_with_headers_should_go_to_infra-backend-v1 (0.02s)
--- FAIL: TestGatewayAPIConformance/HTTPRouteMatching/4_request_to_/v2/example_should_go_to_infra-backend-v2 (30.00s)
--- FAIL: TestGatewayAPIConformance/HTTPRouteMatching/5_request_to_/_with_headers_should_go_to_infra-backend-v2 (30.00s)
--- FAIL: TestGatewayAPIConformance/HTTPRouteMatching/3_request_to_/v2_should_go_to_infra-backend-v2 (30.00s)
FAIL
Similar failure behavior as #430.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/ciCI and build related issuesCI and build related issuesarea/conformanceGateway API Conformance Related IssuesGateway API Conformance Related Issueshelp wantedExtra attention is neededExtra attention is neededkind/bugSomething isn't workingSomething isn't working