ArtifactGC fails when workflows are retried about argo-workflows

[mstrange96]

Also, v3.5.5 is neither :latest nor latest stable. Please fill out the issue template accurately.

All logs etc. are from our v3.5.5 installation, hence why I put it there. I tested :latest as outlined in the template, the bug was still present.

This looks like a duplicate of #12845, which has a fix out in #13066

Indeed it does. I have clearly missed it when searching through passed issues for this bug. Thank you so much, happy to hear you are already working on a fix!

We are enjoying working with Argo-Workflows, it's a great tool 👏

[mstrange96]

Oh, gotcha, sorry about that then. It might be more clear to write "v3.5.5 + :latest" in the "Version" section. Or some folks put a comma separated list of versions they tried. There are unfortunately many users who report bugs on outdated versions (often much more outdated than v3.5.5) so it's something we watch out for 😕

Of course, no worries! I can see how it was not clear to you. I'll keep that in mind in case I report anything in the future 🙂

That's because it was mistakenly filed as a discussion by the user, so it wouldn't pop up on issue search 😅 That's also why I left your issue open, since technically one doesn't exist.

Also GH didn't unify search for Discussions when they made that feature, so things do get lost and duplicated between them 😕 That's one of the reasons I don't turn on Discussions in my personal repos

That makes sense, it's neither the first nor last time this has happened 😅

[agilgur5]

All logs etc. are from our v3.5.5 installation, hence why I put it there. I tested :latest as outlined in the template, the bug was still present.

Oh, gotcha, sorry about that then. It might be more clear to write "v3.5.5 + :latest" in the "Version" section. Or some folks put a comma separated list of versions they tried.
There are unfortunately many users who report bugs on outdated versions (often much more outdated than v3.5.5) so it's something we watch out for 😕

I have clearly missed it when searching through passed issues for this bug.

That's because it was mistakenly filed as a discussion by the user, so it wouldn't pop up on issue search 😅
That's also why I left your issue open, since technically one doesn't exist.

Also GH didn't unify search for Discussions when they made that feature, so things do get lost and duplicated between them 😕 That's one of the reasons I don't turn on Discussions in my personal repos

[agilgur5]

Failed runs have an artifact listed but no storage location - this is only found with the successful run. The artifact gc pod deletes logs and artifacts until an artifact without a storage location is encountered where it produces the error shown from the logs below:

Error: You need to configure artifact storage. More information on how to do this can be found in the docs: https://argo-workflows.readthedocs.io/en/release-3.5/configure-artifact-repository/

This looks like a duplicate of #12845, which has a fix out in #13066

• I have tested with the :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.

Version

v3.5.5

Also, v3.5.5 is neither :latest nor latest stable. Please fill out the issue template accurately.