Closed Ezzahhh closed 2 months ago
time="2024-09-05T00:55:35.267Z" level=info msg="No output artifacts"
It seems no output artifacts. This may have been fixed by #13500. If you use the latest controller, has this issue been resolved?
time="2024-09-05T00:55:35.267Z" level=info msg="No output artifacts"
It seems no output artifacts. This may have been fixed by #13500. If you use the latest controller, has this issue been resolved?
This was also tested on latest tag (index digest f61c2eaf06294f38dc66f7519ae2c3af916ce7dcde8322999789bd39c29e983c) and the finalizer is still not automatically removed
Just a note to others that encounter this. The latest
docker tag does not point to main
. I had to use latest-linux-amd64
. Is this intended? It could be a CI deployment error somewhere. In any case, I believe #13500 should have resolved this but I was testing on the wrong docker tag so will be closing.
Thanks for the help @chengjoey!
Looks like Actions failing https://github.com/argoproj/argo-workflows/actions/runs/10715657770/job/29711546100#step:5:515 due to windows build that's halting the entire job.
@Ezzahhh thanks for analyzing that! I had seen that the Windows build was failing but didn't realize it was causing the combined manifest to fail to run too.
I've filed an issue to get that fixed: #13562
Also since this is indeed resolved on main
, marking this as a duplicate of #13499
Pre-requisites
:latest
image tag (i.e.quay.io/argoproj/workflow-controller:latest
) and can confirm the issue still exists on:latest
. If not, I have explained why, in detail, in my description below.What happened? What did you expect to happen?
When implementing a workflow of workflows pattern and the child workflow uses artifacts, I was not able to delete the jobs after they are complete. Usually able to delete the child pod (the artifact GC finalizer is removed for it) but the parent seems to never have its finalizer removed so it cannot be deleted unless with manual intervention. Removal of the artifact output from the child wf step resolves this issue.
Version(s)
v3.5.10 and index digest on container f61c2eaf06294f38dc66f7519ae2c3af916ce7dcde8322999789bd39c29e983c
Paste a minimal 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