Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

container-kill or pod-network-latency Litmus chaos experiment not working, helper pod is stuck in running state and getting time out. #5030

Open
Pradeep5592 opened this issue Jan 21, 2025 · 0 comments

Comments

@Pradeep5592
Copy link

For container-kill experiment helper pod logs stuck at "injecting chaos in target space" and after some time err: could get container restart count at container-kill.go -> caused by: "https:///api/v1/namespaces//<namespace_name>/pods/<pod_name> " ///dial tcp timeout -> chaos injection failed caused by: STATUS_CHECKS_ERROR reason "container is not completed within timeout" and on "container-kill" pod shows "helper pod running" continuously and after some time "helper pod failed

For network-latency experiment helper pod is stuck at {PreReq]: Getting the ENV variables" and then the error comes is helper pod failed , couldn't get container id by pod.go , dial tcp timeout. and pod-network-latency pod has same as above error.

Also for helper pod owner comes as blank is it fine ?

Experiment and Engine used as given in https://github.com/litmuschaos/chaos-charts/tree/master/faults/kubernetes.

Env - OCP 4.14.30
runtime - crio
Socket_path= /var/run/crio/crio.sock (i also tried /run/crio/crio.sock)
SIGNAL-SIGKILL (in container kill exp)

litmus-admin sa used with privileged access.
go-runner:3.10.0
Litmus version 3.12.0
not using workflows , installed litmus helm charts and then litmus agent helm charts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant