-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.21.0
-
None
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The `GRPCRouteListenerHostnameMatching` Conformance test is flaky, the test stops after a feature surpasses 180s
Version-Release number of selected component (if applicable):
How reproducible:
failed on 2/3 runs
Steps to Reproduce:
1. Run the e2e-aws-gatewayapi-conformance tests
2.
3.
Actual results:
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_cluster-ingress-operator/1306/pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-gatewayapi-conformance/1991143752143474688/artifacts/e2e-aws-gatewayapi-conformance/test/build-log.txt
Expected results:
All tests pass
Additional info: