-
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
Stopped workflow has no artifacts #10337
Comments
3 tasks
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Feb 12, 2023
…rgoproj#10033 argoproj#10490 Signed-off-by: Alex Collins <[email protected]>
8 tasks
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Feb 12, 2023
…rgoproj#10033 argoproj#10490 Signed-off-by: Alex Collins <[email protected]>
8 tasks
alexec
added a commit
that referenced
this issue
Feb 23, 2023
) Signed-off-by: Alex Collins <[email protected]>
33 tasks
terrytangyuan
pushed a commit
that referenced
this issue
Mar 29, 2023
) Signed-off-by: Alex Collins <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pre-requisites
:latest
What happened/what you expected to happen?
I have 'archiveLogs' enabled in my Argo controller.
and
controller.persistence.archive
set totrue
.When I Stop a running Workflow, I expect the archived Workflow to have a list of artifacts of the archived logs.
What happens is that the Workflow's output.artifacts value is empty.
In the 'wait' container, I can see that the logs were successfully archived to S3, and I can also see the log files in S3, but it seems that the Argo controller is not properly saving the output.artifacts associated with the workflow to the Workflow's metadata.
Version
v3.4.4
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
Logs from in your workflow's wait container
The logs below are from our actual Workflow, not the sample workflow I shared in this bug report.
The text was updated successfully, but these errors were encountered: