-
Notifications
You must be signed in to change notification settings - Fork 703
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
"Failed to get argo pod logs" is not intuitive #4532
Comments
Hello @namkyu1999 this error ("mainLogs":"Failed to get argo pod logs") is exactly what I am getting if I want to run any chaosexperiment, any advice what I am doing wrong? Or maybe where I can find more detailed logs..? First time I am installing and trying Litmus.. |
Hi any updates on this, I have the same issue. |
I can see "Failed to get argo pod logs" on node drain experiment. Also, the state of the experiment on the UI updates to "completed" whereas the operation is still going on in the cluster. any update on this? |
still in progress 😢 |
can i take this issue? |
go ahead, @kwx4957 |
hello, are there any updates? I still get the same message
After completion (successful or not), the logs are gone. |
@celinegrn it’s not merged yet, in reviewing process i think if you want to get logs after completing experiment, you can remove podGC field in yaml manifest. In that case, you'll need to delete the experiment pod manually |
Hi Team, Kindly could you guide me on how to remove the podGC from the yaml manifest which u have suggested above, as i am unable to find podGC in my yaml manifest. Attached the screenshot for reference: Also, could u update once fixed. |
When we initiate the chaos experiment,
{"mainLogs":"Failed to get argo pod logs"}
is shown when a workflow is not ready. but IMO, for users, this log message is not intuitive so that they cannot know what it mean exactly (because they even don't know how litmus uses argo workflow).I'm gonna work on this issue and will suggest alternatives.
The text was updated successfully, but these errors were encountered: