From d80981b65749cec0107dfb4637b1b4b27b807c45 Mon Sep 17 00:00:00 2001 From: Clayton Coleman Date: Sun, 8 Mar 2020 16:21:57 -0400 Subject: [PATCH] test: Detect flakes caused by container teardown races on CRI CRI returns a different reason than the dockershim, and we must also catch the symptoms of https://github.com/kubernetes/kubernetes/issues/88766 in that environment. --- test/e2e/node/pods.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/e2e/node/pods.go b/test/e2e/node/pods.go index 657b1ec5f82..ea6855b45fd 100644 --- a/test/e2e/node/pods.go +++ b/test/e2e/node/pods.go @@ -350,7 +350,7 @@ var _ = SIGDescribe("Pods Extended", func() { switch { case t.ExitCode == 1: // expected - case t.ExitCode == 128 && t.Reason == "ContainerCannotRun" && reBug88766.MatchString(t.Message): + case t.ExitCode == 128 && (t.Reason == "StartError" || t.Reason == "ContainerCannotRun") && reBug88766.MatchString(t.Message): // pod volume teardown races with container start in CRI, which reports a failure framework.Logf("pod %s on node %s failed with the symptoms of https://github.com/kubernetes/kubernetes/issues/88766") default: