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.
This commit is contained in:
Clayton Coleman 2020-03-08 16:21:57 -04:00
parent 672aa55ee4
commit d80981b657
No known key found for this signature in database
GPG Key ID: 3D16906B4F1C5CB3

View File

@ -350,7 +350,7 @@ var _ = SIGDescribe("Pods Extended", func() {
switch { switch {
case t.ExitCode == 1: case t.ExitCode == 1:
// expected // 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 // 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") framework.Logf("pod %s on node %s failed with the symptoms of https://github.com/kubernetes/kubernetes/issues/88766")
default: default: