[k8s.io] Pods should not start app containers if init containers fail on a RestartAlways pod {Kubernetes e2e suite}

[k8s-github-robot]

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke/12460/

Failed: [k8s.io] Pods should not start app containers if init containers fail on a RestartAlways pod {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:127
Aug  2 15:26:19.468: Couldn't delete ns "e2e-tests-pods-jauih": an error on the server has prevented the request from succeeding (delete namespaces e2e-tests-pods-jauih)
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:237

[david-mcmahon]

Autoassigned...to me? @lavalamp
@dchen1107 is this a node thing?

[lavalamp]

Check the test owners csv file & find a new owner if you don't think you
should own this test. :)

On Tue, Aug 2, 2016 at 3:48 PM, David McMahon notifications@github.com
wrote:

Autoassigned...to me? @lavalamp https://github.com/lavalamp
@dchen1107 https://github.com/dchen1107 is this a node thing?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#29954 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAnglg9mABKzz9f7EE9a7LXB4bJtIiyoks5qb8lAgaJpZM4JbH94
.

[david-mcmahon]

Ah yes, thanks @lavalamp, the new hotness, test_owners.csv!
#29956

[smarterclayton]

Looking at the test grid, I see no other examples of this flaking.

[lavalamp]

Well, that's why it's only P2 :)

[smarterclayton]

So I know of at least 2-3 Docker related hangs / failures that might result in this symptom. Will try to take a peek at those.

[k8s-github-robot]

[FLAKE-PING] @smarterclayton

This flaky-test issue would love to have more attention...

[k8s-github-robot]

[FLAKE-PING] @smarterclayton

This flaky-test issue would love to have more attention.

[k8s-github-robot]

[FLAKE-PING] @smarterclayton

This flaky-test issue would love to have more attention.

[k8s-github-robot]

[FLAKE-PING] @smarterclayton

This flaky-test issue would love to have more attention.

[smarterclayton]

The last run was due to a GKE break (the test didn't have access to make calls to service accounts). I think the one before that was #32302. Going to close because I haven't seen this recur. We have #29972 to cover that. Note that it is possible for Docker to race and report invalid info (more likely outside of our tests, where we don't control docker version as tightly).