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 fail: Services should serve identically named services in different namespaces on different load-balancers #18952

Closed
gmarek opened this issue Dec 21, 2015 · 12 comments
Closed

e2e fail: Services should serve identically named services in different namespaces on different load-balancers #18952

gmarek opened this issue Dec 21, 2015 · 12 comments
Assignees
@brendandburns
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@gmarek
Copy link
Contributor

gmarek commented Dec 21, 2015

This test reliably fail on gke-test and gke-1.1:
http://kubekins.dls.corp.google.com/view/Critical%20Builds/job/kubernetes-e2e-gke-test/10906/

Services should serve identically named services in different namespaces on different load-balancers

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:861 Expected error: <*exec.ExitError | 0xc20875eee8>: { ProcessState: { pid: 24780, status: 256, rusage: { Utime: {Sec: 0, Usec: 244000}, Stime: {Sec: 0, Usec: 48000}, Maxrss: 32832, Ixrss: 0, Idrss: 0, Isrss: 0, Minflt: 18289, Majflt: 0, Nswap: 0, Inblock: 0, Oublock: 48, Msgsnd: 0, Msgrcv: 0, Nsignals: 0, Nvcsw: 59, Nivcsw: 25, }, }, } exit status 1 not to have occurred

@kubernetes/goog-gke
@ihmccreery please reassign.
@gmarek gmarek added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. kind/flake Categorizes issue or PR as related to a flaky test. labels Dec 21, 2015
@gmarek
Copy link
Contributor Author

gmarek commented Dec 21, 2015

I cleaned up the project to bring it down below quota again. This needs to be monitored.

@ikehz
Copy link
Contributor

ikehz commented Dec 21, 2015

I cleaned up the project to bring it down below quota again. This needs to be monitored.

Am I inferring correctly that we ran out of static IP address quota in the project?

Reassigning to @fejta as this falls squarely inside his projects-as-cattle project.

@ikehz ikehz assigned fejta and unassigned ikehz Dec 21, 2015
@gmarek
Copy link
Contributor Author

gmarek commented Dec 21, 2015

We run also out of networks, firewall rules, backend services and target pools.

@ikehz
Copy link
Contributor

ikehz commented Dec 22, 2015

Note that this test is in the parallel-flaky suite, and after #19021 is merged, it will simply be [Flaky]. It should be cleaned up and moved out of that suite, or added to the [Disruptive] or [Serial] labels.

@goltermann
Copy link
Contributor

This is a P0 flaky test - can we either prioritize and fix, or change priority?

@ikehz ikehz assigned ikehz and unassigned fejta Jan 11, 2016
@ikehz
Copy link
Contributor

ikehz commented Jan 11, 2016

I'll see what I can do.

@ikehz ikehz added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Jan 12, 2016
@ikehz
Copy link
Contributor

ikehz commented Jan 12, 2016

We currently FAIL_ON_GCP_RESOURCE_LEAK for this suite, so I don't think there's much more we can do until #18119 is fixed. Closing.

@ikehz ikehz closed this as completed Jan 12, 2016
@ikehz
Copy link
Contributor

ikehz commented Jan 30, 2016

"Services should serve identically named services in different namespaces on different load-balancers" is still marked as [Flaky] at HEAD. I will send a PR to close this.

@ikehz ikehz reopened this Jan 30, 2016
@ikehz ikehz mentioned this issue Jan 30, 2016
Closed
@ikehz ikehz removed the team/gke label Feb 1, 2016
@ikehz
Copy link
Contributor

ikehz commented Feb 1, 2016

This test is still failing in the -flaky suites, due to out-of-quota for static addresses. I cleaned up the quota and will monitor (there are 4 addresses in the project k8s-jkns-e2e-gce-flaky as of now).

@ikehz
Copy link
Contributor

ikehz commented Feb 1, 2016

Also with #20098 out, if this test seems to be going well for a couple of days, I'll promote it out of [Flaky].

@ikehz ikehz mentioned this issue Feb 1, 2016
Merged
@ikehz ikehz assigned brendandburns and unassigned ikehz Feb 1, 2016
@thockin
Copy link
Member

thockin commented Feb 2, 2016

I don't see how this test could ever pass - the test itself seems deeply broken.

@thockin
Copy link
Member

thockin commented Feb 2, 2016

dup of #16285

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

@brendandburns brendandburns

Labels
kind/flake Categorizes issue or PR as related to a flaky test. 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
6 participants
@ikehz @fejta @gmarek @thockin @brendandburns @goltermann