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
Flake: Services should serve identically named services in different namespaces on different load-balancers #16285
Comments
Looks like this e2e code hasn't changed since |
Ugh. What changed is that we moved it off teh flaky list. Perhaps wrongly On Mon, Oct 26, 2015 at 11:17 AM, Stephen Milner notifications@github.com
|
Ah, I see. 6600fbc removed a number of e2e service items from - "Services.*identically\snamed" |
the test is actually still running Saad's fix where we correctly wait for GCE operations to complete, is checked in. Closing this issue. |
Looks like this test is failing forever in http://kubekins.dls.corp.google.com/view/Flaky/job/kubernetes-e2e-gce-parallel-flaky and http://kubekins.dls.corp.google.com/view/Flaky/job/kubernetes-e2e-gce-flaky.
|
Somehow I lost this one. Will look at it ASAP On Thu, Jan 21, 2016 at 3:13 PM, Janet Kuo notifications@github.com wrote:
|
The problem is that this test depends on the api proxy which doesn't do UDP, as far as I can tell, so it could never have worked when UDP support was added. I will see what I can do to rectify. |
Fixed test is #20426 - it's a doozy. |
I've asked oncall to move this to the head of the queue. It's hard to figure out existing flakes when the test driving them has been totally changed. I want to re-examine all e2e/service.go flakes after tghis |
#20426 is in. I am going to close a few issues and wait for reoccurence, which is to be handled P(-1) |
Blocking merges, P0
http://kubekins.dls.corp.google.com/view/Critical%20Builds/job/kubernetes-e2e-gce-parallel/10319/
The text was updated successfully, but these errors were encountered: