-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Unable to view log if pod get killed due activeDeadlineSeconds #7081
Comments
@tczhao Can you try v3.2.3 which has POD Name fix? |
doesn't work with the current master, I don't think it's related to pod name |
@tczhao we struggled to understand the problem, so let me play it back: When a pod exceeds its deadline, the Why does this happen please? |
Hi @alexec
The proposed solution in the PR (for emissary part) is to
logs after deadlineExceeded Emissary
PNS with #7092 fix
|
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. |
Summary
What happened/what you expected to happen?
With emissary
If a pod error exit due workflow activeDeadlineSeconds, log is saved.
However, because the output artifact does not appear in workflow.status.nodeid, users are not able to view log from UI
artifact not found
Viewing log works If a pod error exit due program error, container log is saved and output field are added in workflow.status.nodeid
What version of Argo Workflows are you running?
~v3.2.1
Diagnostics
Workflow
Wait container log
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: