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

"Failed to get argo pod logs" is not intuitive #4532

Open
namkyu1999 opened this issue Mar 15, 2024 · 6 comments · May be fixed by #4926
Open

"Failed to get argo pod logs" is not intuitive #4532

namkyu1999 opened this issue Mar 15, 2024 · 6 comments · May be fixed by #4926
Assignees

Comments

@namkyu1999
Copy link
Member

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.

@lacike200
Copy link

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..

@hafeezahmed-hub
Copy link

Hi any updates on this, I have the same issue.

@pratik705
Copy link

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?

@namkyu1999
Copy link
Member Author

still in progress 😢

@kwx4957
Copy link
Contributor

kwx4957 commented Sep 18, 2024

can i take this issue?

@namkyu1999 namkyu1999 assigned kwx4957 and unassigned namkyu1999 Sep 18, 2024
@namkyu1999
Copy link
Member Author

can i take this issue?

go ahead, @kwx4957

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

5 participants