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

[Flaky Test] gce-master-scale-correctness (ci-kubernetes-e2e-gce-scale-correctness) #87142

Open
droslean opened this issue Jan 13, 2020 · 8 comments

Comments

@droslean
Copy link
Member

@droslean droslean commented Jan 13, 2020

Which jobs are failing:
gce-master-scale-correctness (ci-kubernetes-e2e-gce-scale-correctness)

Which test(s) are failing:
[sig-network] Networking Granular Checks: Services should update nodePort: udp [Slow]

Since when has it been failing:
01-12 04:02 PST

Testgrid link:
https://testgrid.k8s.io/sig-release-master-informing#gce-master-scale-correctness

Reason for failure:

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/networking.go:251
Jan 12 12:31:12.348: Failed to find expected endpoints:
Tries 130
Command echo hostName | nc -w 1 -u 34.73.150.156 30966
retrieved map[netserver-0:{} netserver-1:{} netserver-2:{} netserver-3:{} netserver-4:{} netserver-5:{} netserver-6:{} netserver-7:{} netserver-8:{} netserver-9:{}]
expected map[]

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/network/utils.go:381

Anything else we need to know:
/cc @kubernetes/ci-signal
/sig network
/milestone v1.18
/priority critical-urgent

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

@k8s-ci-robot k8s-ci-robot commented Jan 13, 2020

@droslean: The provided milestone is not valid for this repository. Milestones in this repository: [next-candidate, v1.13, v1.14, v1.15, v1.16, v1.17, v1.18, v1.19, v2.0]

Use /milestone clear to clear the milestone.

In response to this:

Which jobs are failing:
gce-master-scale-correctness (ci-kubernetes-e2e-gce-scale-correctness)

Which test(s) are failing:
[sig-network] Networking Granular Checks: Services should update nodePort: udp [Slow]

Since when has it been failing:
01-12 04:02 PST

Testgrid link:
https://testgrid.k8s.io/sig-release-master-informing#gce-master-scale-correctness

Reason for failure:

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/network/networking.go:251
Jan 12 12:31:12.348: Failed to find expected endpoints:
Tries 130
Command echo hostName | nc -w 1 -u 34.73.150.156 30966
retrieved map[netserver-0:{} netserver-1:{} netserver-2:{} netserver-3:{} netserver-4:{} netserver-5:{} netserver-6:{} netserver-7:{} netserver-8:{} netserver-9:{}]
expected map[]

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/network/utils.go:381

Anything else we need to know:
/cc @kubernetes/ci-signal
/sig network
/milestone v.1.18
/priority critical-urgent

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@droslean

This comment has been minimized.

Copy link
Member Author

@droslean droslean commented Jan 13, 2020

/milestone v1.18

@athenabot

This comment has been minimized.

Copy link

@athenabot athenabot commented Jan 13, 2020

/triage unresolved

Comment /remove-triage unresolved when the issue is assessed and confirmed.

🤖 I am a bot run by vllry. 👩‍🔬

@droslean

This comment has been minimized.

Copy link
Member Author

@droslean droslean commented Jan 14, 2020

/remove-kind failing-test
/kind flake

@droslean droslean changed the title [Failing Test] gce-master-scale-correctness (ci-kubernetes-e2e-gce-scale-correctness) [Flaky Test] gce-master-scale-correctness (ci-kubernetes-e2e-gce-scale-correctness) Jan 14, 2020
@bowei

This comment has been minimized.

Copy link
Member

@bowei bowei commented Jan 16, 2020

/assign

@bowei

This comment has been minimized.

Copy link
Member

@bowei bowei commented Jan 16, 2020

cc: @robscott this is related to endpoints

@robscott

This comment has been minimized.

Copy link
Member

@robscott robscott commented Jan 17, 2020

@droslean Has this been failing elsewhere? I'm only seeing the 1 failure for that job in the Prow history for gce-master-scale-correctness going back to November. From what I can tell, 1/10 endpoints weren't created within the timeout window on this failure. This seems like it may not be a critical/urgent bug. For now I'm reprioritizing this to a lower level, but definitely let me know if we need to resolve this more urgently.

/priority important-soon

@robscott

This comment has been minimized.

Copy link
Member

@robscott robscott commented Jan 17, 2020

/remove-priority critical-urgent
/remove-triage unresolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
CI Signal team (SIG Release)
  
New (no response yet)
5 participants
You can’t perform that action at this time.