-
Notifications
You must be signed in to change notification settings - Fork 182
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
err: Unable to Get the chaosengine #366
Comments
cc: @ispeakc0de |
@niebomin could you please provide the logs for following pods:
The |
Thanks for the response. The environment was taken down. Will take a while to get it back. |
Command:
pod-delete-lddg4u-wmtmm status is Error Command: Output:
Operator log: Engine describe: |
I kind of think it's because the |
This is interesting. @ispeakc0de do you have a comment on this? The error is in being able to access chaosengine object by the experiment pod - until then the operator and runner are successfully able to generate events against it. @niebomin was the error a one off or do you see that everytime you run the experiment on 1.9.0? Also, just to confirm were you using the chaosexperiment CR also specific to 1.9.0? (https://hub.litmuschaos.io/api/chaos/1.9.0?file=charts/generic/pod-delete/experiment.yaml) |
I can see it every time. I downloaded the source, and was using the yaml file locally. |
My environment is pretty simple. I have an azure k8s cluster, and followed this guide
https://istio.io/latest/docs/setup/getting-started/
to setup my environment. In other words, the namespace is enabled with istio injection.Litmus is setup, and I was trying to run pod-delete experiment. Chaos runner pod is created, but I saw errors though. "pod-delete" pod is also created, but the target pod was not deleted. When I was looking at logs by
k logs -f pod-delete-4y48y4-ql64c -c pod-delete-4y48y4
, I saw errorThis is my engine yaml, https://drive.google.com/file/d/1HAaMLamHS3BZP6SDNtD_-YO1pdl46vnh/view?usp=sharing
Litmus version is 1.9.0
The text was updated successfully, but these errors were encountered: