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

fix e2e test: Services should be able to create a functioning NodePort service #15253

Closed
deads2k opened this issue Jul 18, 2017 · 0 comments · Fixed by #15766
Closed

fix e2e test: Services should be able to create a functioning NodePort service #15253

deads2k opened this issue Jul 18, 2017 · 0 comments · Fixed by #15766

Comments

@deads2k
Copy link
Contributor

deads2k commented Jul 18, 2017

Specifically Extended.[k8s.io] Services should be able to create a functioning NodePort service

I think that this is intended to be the fix: kubernetes/kubernetes#49025, but I'm not completely certain.

It was disabled in disable a few failing e2e tests from #15234 and that is green and reviewed, so its a good base.

@deads2k deads2k added this to the 3.7.0 milestone Jul 18, 2017
@deads2k deads2k mentioned this issue Jul 18, 2017
56 tasks
@danwinship danwinship assigned danwinship and unassigned dcbw Aug 12, 2017
openshift-merge-robot added a commit that referenced this issue Sep 18, 2017
Automatic merge from submit-queue (batch tested with PRs 16226, 16377, 15766, 16299, 16153)

Fix NodePort test

Pulls in the k8s test utils fix from kubernetes/kubernetes#49025 to make the NodePort test work on non-cloud installs again.

Fixes #15253
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants