CC @ArtfulCoder, @thockin

It might have uncovered a real test configuration issue.

Sent from my iPhone

On Dec 1, 2015, at 9:02 PM, Fabio Yeon notifications@github.com wrote:

CC @ArtfulCoder, @thockin

—
Reply to this email directly or view it on GitHub.

Labelling this PR as size/S

It's possible. But I'm unfamiliar with the test involved (pod seems to run some sort of script). Merge bot is stopped due to this test failing. Would you prefer we wait until test owners (in Poland?) have a chance to debug?

GCE e2e test build/test passed for commit 7100d27.

• Build Log
• Test Artifacts
• Internal Jenkins Results

Since we have blocked mergebot now, I think we can merge it asap.

LGTM

@gmarek

Merging to unblock the bot.

@thockin @ArtfulCoder @gmarek

Just to give more clear context why we decided to revert it.

it broke kubemark-gce, which is currently a blocking build for mergebot
A bit more context.

in kubemark, there is no skydns (we want to add it at some point, but that's not done yet)
however, with this PR merge, this caused that no pods were started (all the pods were successfully created & scheduled, but not even a single pod was started)
note, that we are using "pause" images, which aren't the most demanding ones :)

So I think the question is the following:
if this change requires DNS to start any pod, it has be clearly stated (I'm not saying it's not reasonable - it makes sense to say that).
However, if it wasn't the intention of this PR, then there was some bug in it.