-
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 download Artifacts from the Archived Workflows UI (v3.4.3) #9968
Comments
@tczhao Would you like to take a look? |
Sure.
|
@tczhao Are you going to work on these issues? |
I'm seeing this issue reproduce in v3.5.4 with the same kind of error
how do I reopen this? |
You don't; it's a new bug in a different version (the previous one was fixed over a year ago), so you'd open a new bug report.
There was a similar bug in 3.5 reported in #12331, but that was fixed in #12397. It seems like that didn't make it into 3.5.4 -- it is slated for the next patch release: #11997 (comment) |
Pre-requisites
:latest
What happened/what you expected to happen?
I ran a simple artifact-passing workflow that created a text file artifact. When I click on the artifact in the Argo UI on the "Workflow" page, I can see the contents of the artifact come up in the UI. But, after the workflow is archived and deleted, the UI on the "Archived Workflow" page displays an "Internal Server Error", with
error="workflows.argoproj.io \"artifact-passing-9rzv7\" not found"
message on the argo-server logs.Note that this happens right after the workflow is deleted from the "Workflows" UI. Before it was deleted, I can see the Artifacts normally even in the "Archived Workflows" UI (When the same workflow appears at the same time on "Workflows" and "Archived Workflows" UI).
Furthermore, on the same "Archived Workflows" page, when I click on the container node -> INPUTS/OUTPUTS -> artifact, Argo is able to successfully retrieve the artifact (with the URL pointing to:
https://<argo-server-url>/artifact-files/<username>/archived-workflows/a093e078-097a-4ab6-b51f-3e0b62123265/artifact-passing-9rzv7-2621575856/outputs/hello-art
).I think this might be related with the previous issue -- Argo UI - Cannot View Artifact in Archived Workflows. (ref: #9858)
Here is a screenshot of the error in the "Archived Workflows" UI:
Here is a screenshot of normal Artifacts viewer in the "Workflows" UI before the workflow was archived and deleted:
What you expected to happen?
I expected to be able to view and download the artifact in the Archived Workflows UI, just as I was able to view it before the workflow was archived and deleted. I was able to download Artifacts normally in Argo v3.3.7.
Version
v3.4.3
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
workflow-controller logs doesn't show error, here is the error shown in the argo-server logs.
Logs from in your workflow's wait container
kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded
The text was updated successfully, but these errors were encountered: