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

k8s Unit Test Flake: TestServiceRegistryExternalTrafficBetaAnnotationHealthCheckNodePortUserAllocation #13693

Closed
stevekuznetsov opened this issue Apr 9, 2017 · 3 comments
Assignees
Labels
area/tests component/kubernetes kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P2 vendor-update Touching vendor dir or related files

Comments

@stevekuznetsov
Copy link
Contributor

=== RUN   TestServiceRegistryExternalTrafficBetaAnnotationHealthCheckNodePortUserAllocation
--- FAIL: TestServiceRegistryExternalTrafficBetaAnnotationHealthCheckNodePortUserAllocation (0.00s)
	rest_test.go:1012: Unexpected failure creating service Internal error occurred: Failed to allocate requested HealthCheck nodePort 30200: provided port is already allocated
panic: interface conversion: interface is nil, not *api.Service [recovered]
	panic: interface conversion: interface is nil, not *api.Service

goroutine 86 [running]:
panic(0x16cc7a0, 0xc4201c30c0)
	/usr/local/go/src/runtime/panic.go:500 +0x1ae
testing.tRunner.func1(0xc42041d440)
	/usr/local/go/src/testing/testing.go:579 +0x474
panic(0x16cc7a0, 0xc4201c30c0)
	/usr/local/go/src/runtime/panic.go:458 +0x271
github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/registry/core/service.TestServiceRegistryExternalTrafficBetaAnnotationHealthCheckNodePortUserAllocation(0xc42041d440)
	/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/registry/core/service/rest_test.go:1014 +0x58c
testing.tRunner(0xc42041d440, 0x198a298)
	/usr/local/go/src/testing/testing.go:610 +0xca
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:646 +0x530

seen here

upstream: kubernetes/kubernetes#37982

@derekwaynecarr
Copy link
Member

this is fixed upstream:
kubernetes/kubernetes#46060

we could pick this in origin or wait for next rebase. since flakes slow everyone down, i am inclined to pick it after master goes out.

@jboyd01 -- can you look at picking this change from upstream kube to origin? it's relatively small, and is a good example to teach you of the process.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 13, 2018
@stevekuznetsov
Copy link
Contributor Author

Picked up in the rebase

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tests component/kubernetes kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P2 vendor-update Touching vendor dir or related files
Projects
None yet
Development

No branches or pull requests

4 participants