From 4619a89ebaa6c4e822e1772ded0e89f78751f350 Mon Sep 17 00:00:00 2001 From: Maciej Szulik Date: Thu, 30 Jan 2025 19:07:28 +0100 Subject: [PATCH] e2e: expand error conditions when test-ing port-forward Signed-off-by: Maciej Szulik --- test/e2e/kubectl/portforward.go | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/test/e2e/kubectl/portforward.go b/test/e2e/kubectl/portforward.go index 3ebf3f00279..f2b57635f79 100644 --- a/test/e2e/kubectl/portforward.go +++ b/test/e2e/kubectl/portforward.go @@ -617,7 +617,8 @@ var _ = SIGDescribe("Kubectl Port forwarding", func() { // this error indicates timeout when POST-ing data gomega.ContainSubstring("context deadline exceeded"), // this will happen when trying to write to a closed connection - gomega.ContainSubstring("write: broken pipe"), gomega.ContainSubstring("closed network connection"))) + gomega.ContainSubstring("write: broken pipe"), gomega.ContainSubstring("closed network connection"), + gomega.ContainSubstring("connect: connection refused"))) ginkgo.By("Check kubectl port-forward exit code") gomega.Expect(cmd.cmd.ProcessState.ExitCode()).To(gomega.BeNumerically("<", 0), "kubectl port-forward should finish with non-zero exit code")