Skip to content
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

TestTraffic/sniffing/auto-tcp_a->headless_from_cluster-0 flakes frequently #26798

Closed
hzxuzhonghu opened this issue Aug 25, 2020 · 7 comments
Closed
Labels
area/networking lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while

Comments

@hzxuzhonghu
Copy link
Member

https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/26638/integ-pilot-k8s-tests_istio/18950

@howardjohn has some fix recently

@istio-policy-bot
Copy link

🤔 ❄️ Hey there's been no update for this test flakes for 3 days.

Courtesy of your friendly test flake nag.

@stevenctl
Copy link
Contributor

I think this is fixed for single cluster, will wait a couple days now that it's re-enabled before closing this.

We still get some failures on http/grpc in multicluster mode. I think we're hitting limits on our test infra, can't replicate in GKE clusters.

=== RUN   TestTraffic/sniffing/auto-http_a->vm_from_cluster-1
2020-09-09T17:17:59.568511Z	info	tf	=== BEGIN: Test: 'pilot[TestTraffic/sniffing/auto-http_a->vm_from_cluster-1]' ===
    traffic.go:69: call for auto-http a->vm from cluster-1/0 failed, retrying: failed calling a->'http://vm.echo-1-70707.svc.cluster.local:81/': rpc error: code = Unknown desc = 20/20 requests had errors; first error: Get "http://vm.echo-1-70707.svc.cluster.local:81": read tcp 10.20.0.10:59864->10.255.20.200:81: read: connection reset by peer

@stevenctl
Copy link
Contributor

We've disabled TCP sniffing tests so this passes but it isn't fixed yet. In the multicluster pilot job I see a lot of connection resets for http/grpc.

@istio-policy-bot istio-policy-bot added the lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while label Dec 23, 2020
@istio-policy-bot istio-policy-bot added the lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. label Jan 7, 2021
@howardjohn
Copy link
Member

Not stale

@howardjohn howardjohn reopened this Mar 19, 2021
@istio-policy-bot istio-policy-bot removed the lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while label Mar 19, 2021
@istio-policy-bot istio-policy-bot added the lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while label Jun 18, 2021
@stevenctl
Copy link
Contributor

Not stale

@istio-policy-bot istio-policy-bot removed the lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while label Jun 18, 2021
@istio-policy-bot istio-policy-bot added the lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while label Sep 17, 2021
@istio-policy-bot
Copy link

🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2021-06-18. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions.

Created by the issue and PR lifecycle manager.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while
Projects
None yet
Development

No branches or pull requests

4 participants