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.

Sign up for GitHub

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

Jump to bottom

e2e flake: services: should prevent NodePort collisions #25392

Closed
thockin opened this issue May 10, 2016 · 1 comment
Closed

e2e flake: services: should prevent NodePort collisions #25392

thockin opened this issue May 10, 2016 · 1 comment
Assignees
@girishkalele
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@thockin
Copy link
Member

thockin commented May 10, 2016 

[It] should prevent NodePort collisions
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:771
STEP: creating service nodeport-collision-1 with type NodePort in namespace e2e-tests-services-mn51y
STEP: creating service nodeport-collision-2 with conflicting NodePort
May  8 09:52:09.240: INFO: Created service with conflicting NodePort: kind:"" apiVersion:"" 
STEP: deleting service nodeport-collision-1 in namespace e2e-tests-services-mn51y
STEP: deleting service nodeport-collision-2 in namespace e2e-tests-services-mn51y
[AfterEach] [k8s.io] Services


...




• Failure [17.509 seconds]
[k8s.io] Services
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:502
  should prevent NodePort collisions [It]
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:771

  May  8 09:52:09.240: Created service with conflicting NodePort: kind:"" apiVersion:"" 

  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:759
@thockin thockin self-assigned this May 10, 2016
@thockin thockin added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label May 10, 2016
@thockin thockin mentioned this issue May 10, 2016
Merged
@thockin thockin assigned girishkalele and unassigned thockin Jul 15, 2016
@girishkalele
Copy link

@thockin This flake hasn't happened again - close for now ?

@thockin thockin closed this as completed Sep 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@girishkalele girishkalele

Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@thockin @saad-ali @girishkalele