From ffa7157907ad6f7a7e1b6d92090de2930416d08c Mon Sep 17 00:00:00 2001 From: Zahari Dichev Date: Thu, 8 Oct 2020 23:06:03 +0300 Subject: [PATCH] Add warnings for failed secred mounts to expect warnings in it (#5053) Seems that Helm is cleaning orphaned resources. Pods that depend on them seem to be not upgraded on time, causing some warnings to be emitted and he CI process to fail Signed-off-by: Zahari Dichev --- testutil/logs_events.go | 1 + 1 file changed, 1 insertion(+) diff --git a/testutil/logs_events.go b/testutil/logs_events.go index e270d1b91..c5121ec09 100644 --- a/testutil/logs_events.go +++ b/testutil/logs_events.go @@ -43,6 +43,7 @@ var ( knownEventWarningsRegex = regexp.MustCompile(strings.Join([]string{ `MountVolume.SetUp failed for volume .* : couldn't propagate object cache: timed out waiting for the condition`, // pre k8s 1.16 `MountVolume.SetUp failed for volume .* : failed to sync .* cache: timed out waiting for the condition`, // post k8s 1.16 + `MountVolume.SetUp failed for volume "tls" : secret "linkerd-.*" not found`, `(Liveness|Readiness) probe failed: HTTP probe failed with statuscode: 50(2|3)`, `(Liveness|Readiness) probe failed: Get http://.*: dial tcp .*: connect: connection refused`, `(Liveness|Readiness) probe failed: Get http://.*: read tcp .*: read: connection reset by peer`,