Skip to content

Conformance test runner cannot connect to NKG Pods #771

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kate-osborn opened this issue Jun 21, 2023 · 0 comments · Fixed by #787
Closed

Conformance test runner cannot connect to NKG Pods #771

kate-osborn opened this issue Jun 21, 2023 · 0 comments · Fixed by #787
Assignees
Labels
bug Something isn't working refined Requirements are refined and the issue is ready to be implemented.
Milestone

Comments

@kate-osborn
Copy link
Contributor

Describe the bug
The conformance tests send traffic to the IPs of the NKG Pod for the corresponding Gateway. However, all tests that send traffic are failing with:

http.go:217: Request failed, not ready yet: Get "http://<POD-IP>": dial tcp <POD-IP>80: i/o timeout (after 26µs)

and

http.go:217: Request failed, not ready yet: Get "http://<POD-IP>/": context deadline exceeded (after 22.3µs)

To Reproduce
Steps to reproduce the behavior:

  1. Run conformance tests. If you don't want to run the whole suite, run HTTPExactPathMatching test. This will reproduce the error.

Expected behavior
Test runner should be able to connect to the NKG Pod and get a response back from nginx.

Your environment

  • NKG edge

Additional context
This error occurs in 16 tests so it is critical that we fix this bug.

@kate-osborn kate-osborn added the bug Something isn't working label Jun 21, 2023
@mpstefan mpstefan added this to the v0.4.0 milestone Jun 21, 2023
@mpstefan mpstefan added the refined Requirements are refined and the issue is ready to be implemented. label Jun 21, 2023
@ciarams87 ciarams87 self-assigned this Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working refined Requirements are refined and the issue is ready to be implemented.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants