From d02359e094bcffaf035937161efd596ae9cf386e Mon Sep 17 00:00:00 2001 From: Alejandro Pedraza Date: Thu, 18 Jun 2020 15:50:51 -0500 Subject: [PATCH] Int tests: Warn (instead of erroring) upon pod restarts, part two (#4637) In #4595 we stopped failing integration tests whenever a pod restarted just once, which is being caused by containerd/containerd#4068. But we forgot to remove the warning event corresponding to that containerd failure, and such unexpected event continues to fail the tests. So this change adds that event to the list of expected ones. --- testutil/logs_events.go | 1 + 1 file changed, 1 insertion(+) diff --git a/testutil/logs_events.go b/testutil/logs_events.go index bb12ba273..16ae3fd03 100644 --- a/testutil/logs_events.go +++ b/testutil/logs_events.go @@ -48,6 +48,7 @@ var ( `(Liveness|Readiness) probe failed: Get http://.*: net/http: request canceled .*\(Client\.Timeout exceeded while awaiting headers\)`, `Failed to update endpoint .*/linkerd-.*: Operation cannot be fulfilled on endpoints "linkerd-.*": the object has been modified; please apply your changes to the latest version and try again`, `error killing pod: failed to "KillPodSandbox" for ".*" with KillPodSandboxError: "rpc error: code = Unknown desc`, + `failed to create containerd task: failed to start io pipe copy: unable to copy pipes: containerd-shim: opening w/o fifo "/run/containerd/io.containerd.grpc.v1.cri/containers/linkerd-proxy/io/\d+/linkerd-proxy-stdout"`, }, "|")) )