-
Notifications
You must be signed in to change notification settings - Fork 338
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
bug: e2e test will fail randomly #751
Labels
bug
Something isn't working
CI
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
Comments
Good catch |
So, I think we should not watch |
Should only be watched in UDP case? |
Yes, I think so. |
I will fix this issue |
4 tasks
It seems that the recent e2e is running relatively stable, and related PRs have also been merged, can we close this issue? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
CI
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Issue description
Because we test UDP route by using kube-dns as backend, we create route in kube-system namespace. But we run e2e in 2 nodes mode, as a result, when the UDP route case is executing, it will affect the accuracy of other cases, because the ingress controller in other cases will also get this UDP route.
![image](https://user-images.githubusercontent.com/22141303/141255278-24f40715-85f7-4de8-9c72-ec0589564711.png)
This is why e2e failed this time: https://github.com/apache/apisix-ingress-controller/runs/4173189172?check_suite_focus=true
The text was updated successfully, but these errors were encountered: