e2e: add pod/container info in error form exec in pod.

When running connectivity tests, it's up to debug logs to provide information on failure errors. This is not always the case, making it hard to understand where to start investigating errors. This adds pod/container to the error message for calls to k8s exec to make it easier to understand where the issue occured. Signed-off-by: Tom Hadlaw <[email protected]>
cilium · Nov 6, 2023 · d1ad966 · d1ad966
1 parent dacac93
commit d1ad966
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/k8s/client.go b/k8s/client.go
@@ -433,11 +433,11 @@ func (c *Client) ExecInPod(ctx context.Context, namespace, pod, container string
 		Command:   command,
 	})
 	if err != nil {
-		return bytes.Buffer{}, err
+		return bytes.Buffer{}, fmt.Errorf("error with exec request (pod=%s/%s, container=%s): %w", namespace, pod, container, err)
 	}
 
 	if errString := result.Stderr.String(); errString != "" {
-		return bytes.Buffer{}, fmt.Errorf("command failed: %s", errString)
+		return bytes.Buffer{}, fmt.Errorf("command failed (pod=%s/%s, container=%s): %q", namespace, pod, container, errString)
 	}
 
 	return result.Stdout, nil