RequestMirroring Conformance tests are failing

[ciarams87]

Describe the bug
RequestMirroring Conformance tests are failing

To Reproduce
Enable the HTTPRouteRequestMirror and HTTPRouteRequestMultipleMirrors tests in the conformance Makefile and run the conformance tests

Expected behavior
The tests pass

Additional context
This seems like it's coming from a misconfiguration in the test setup - the functionality is working, but the test is unable to find the log output it is expecting. See #3348 (comment)

[sjberman]

kubernetes-sigs/gateway-api#3708 was meant to fix an issue with this test, but I don't think it necessarily did. The timer starts after the initial requests are sent, so if the responses are sent before the timer starts, then when the test looks at the logs since that timer, it won't find the responses.

NGINX must just be so fast that it's beating the test :) this may need an additional fix in the Gateway API repo and then picked up in the next release.

It's a shame because we can't put Mirroring in the conformance report to advertise that we support it until this is fixed.

[salonichf5]

Conformance tests still failing for HTTPRouteRequestMirror and HTTPRouteRequestMultipleMirrors. Manually tested all the cases for request-mirror and request-multiple-mirror and they pass. So functionality looks good.

[sjberman]

I think what we need to do is see if the the fix involves updating the logic in the test itself relating to the timing of grabbing the logs, per my earlier comment on the issue. This will help us know for sure that it's an issue in the test and not in our code.

[salonichf5]

I think what we need to do is see if the the fix involves updating the logic in the test itself relating to the timing of grabbing the logs, per my earlier comment on the issue. This will help us know for sure that it's an issue in the test and not in our code.

Verified by updating the log collection time by 5 mins, 30 mins and an hour but still saw failures. Upon further discussion with you offline, verified the log contents. It is empty for all cases. Logs need to be written by them to the pods, so would be wise to open a discussion in Gateway API repo about this behaviour?