-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Cluster teardown and bring up for GCE e2e not working #5451
Comments
@zmerlynn @jlowdermilk |
This is really cc @brendandburns, but are you synced to past #5448? |
Building from HEAD and trying again I get stuck at the dots -- I've done this N times.
|
@roberthbailey @a-robinson apologies -- this is blocking my progress on addressing your kind review comments for the e2e cluster level logging test #5269 |
If you have the full kube-up output, can you dump it in a gist? |
I do get:
|
But here you go:
|
It could be me. My brain is mush after being call for two days. |
How long did you wait before killing it? Could just be gce slowness. |
Various durations including one > 20 minutes. On Fri, Mar 13, 2015 at 4:24 PM, Jeff Lowdermilk notifications@github.com
|
How many more dotes do you want to see?
|
Switching to a different GCE project makes everything work. |
You probably have some resource that's screwed up and not getting torn down On Fri, Mar 13, 2015 at 5:02 PM, Satnam Singh notifications@github.com
|
Several times I went into Dev Console and deleted all stray resources manually -- it did not help. |
I'm disturbed there were stray resources after kube-down... On Fri, Mar 13, 2015 at 5:16 PM, Satnam Singh notifications@github.com
|
I deleted all of my clusters.
|
Let's livedebug on IRC. |
@satnam6502 @zmerlynn Was there a verdict from IRC livedebug? |
Not enough whisky. Or we need to delete the e2e network and retry. |
The text was updated successfully, but these errors were encountered: