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

[GCE] [Failing Test] conformance nodePort tests #99

Closed
amwat opened this issue Mar 2, 2021 · 2 comments · Fixed by #100
Closed

[GCE] [Failing Test] conformance nodePort tests #99

amwat opened this issue Mar 2, 2021 · 2 comments · Fixed by #100
Labels
sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@amwat
Copy link
Contributor

amwat commented Mar 2, 2021

https://testgrid.k8s.io/conformance-all#Conformance%20-%20GCE%20-%20master%20-%20kubetest2

xref: kubernetes/enhancements#2464

After moving to config-test.sh in #96 the default GCE network name changed from default to e2e-test-${USER}
so changes initially added in #34 are not taking effect.

/cc @BenTheElder @spiffxp
@amwat amwat mentioned this issue Mar 2, 2021
Merged
@BenTheElder
Copy link
Member

and the gce network name breaks the test...? 😬

@amwat
Copy link
Contributor Author

amwat commented Mar 2, 2021

The tests need extra setup to open up the nodePort range which needs to know the name of the network, we were defaulting to the wrong one.

@spiffxp spiffxp added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label Aug 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[GCE] Explicitly set KUBE_GCE_NETWORK amwat/kubetest2
3 participants
@spiffxp @BenTheElder @amwat