[Flaky Test]: TestOtelKubeStackHelm/managed_helm_kube-stack_operator_standalone_agent_kubernetes_privileged – context deadline exceeded

[pkoutsovasilis]

Failing test case

TestOtelKubeStackHelm/managed_helm_kube-stack_operator_standalone_agent_kubernetes_privileged

Error message

context deadline exceeded

Build

https://buildkite.com/elastic/elastic-agent-extended-testing/builds/7563#01953a3a-ec4e-4117-a689-2b09546c7290/56-333

OS

Linux

Stacktrace and notes

FAIL
FAIL	github.com/elastic/elastic-agent/testing/integration	756.559s
=== Failed
=== FAIL: testing/integration TestOtelKubeStackHelm/managed_helm_kube-stack_operator_standalone_agent_kubernetes_privileged (137.81s)
    kubernetes_agent_standalone_test.go:1618:
        	Error Trace:	/opt/buildkite-agent/builds/bk-agent-prod-gcp-1740438717215447480/elastic/elastic-agent-extended-testing/testing/integration/kubernetes_agent_standalone_test.go:1618
        	            				/opt/buildkite-agent/builds/bk-agent-prod-gcp-1740438717215447480/elastic/elastic-agent-extended-testing/testing/integration/otel_helm_test.go:144
        	            				/opt/buildkite-agent/builds/bk-agent-prod-gcp-1740438717215447480/elastic/elastic-agent-extended-testing/testing/integration/otel_helm_test.go:125
        	Error:      	Received unexpected error:
        	            	context deadline exceeded
        	Test:       	TestOtelKubeStackHelm/managed_helm_kube-stack_operator_standalone_agent_kubernetes_privileged
        	Messages:   	failed to install helm chart
    kubernetes_agent_standalone_test.go:1600: failed to dump logs: error getting container kube-rbac-proxy of pod kube-stack-otel-opentelemetry-operator-6588cdb6bc-c7s6c logs: container "kube-rbac-proxy" in pod "kube-stack-otel-opentelemetry-operator-6588cdb6bc-c7s6c" is waiting to start: ContainerCreating
        error getting container manager of pod kube-stack-otel-opentelemetry-operator-6588cdb6bc-c7s6c logs: container "manager" in pod "kube-stack-otel-opentelemetry-operator-6588cdb6bc-c7s6c" is waiting to start: ContainerCreating

this seems like a really rare transient one. Most probably is caused by external dependencies short outage but let's keep an issue about it for future reference

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)