Non-transient error: <nil>

[black-snow]

Pre-requisites

• I have double-checked my configuration
• 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.
• I have searched existing issues and could not find a match for this bug
• I'd like to contribute the fix myself (see contributing guide)

What happened? What did you expect to happen?

I encounter a lot of these:

Non-transient error: <nil>

and sadly there's not much context I can give. Actually, I can give close to nil context. ;)

We run workflows with up to 250 nodes and thousands of concurrent pods. The above log is apparenty just a warning but the nil there seems worrisome. Should I worry?

Sadly, I cannot provide proper steps to reproduce. This ain't very helpful but perhaps someone else is seeing the same or has an immediate idea.

Version(s)

v3.5.12

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.

N/A

Logs from the workflow controller

time="2024-11-08T10:02:19.639Z" level=warning msg="Non-transient error: <nil>"

Logs from in your workflow's wait container

N/A

[tooptoop4]

@black-snow provide the controller logs surrounding that line

[isubasinghe]

This is not really actually an issue, there is a bug where we call IsTransientError on an nil error.

[black-snow]

Thanks for looking into this. Do you still need the surrounding logs?
Can we get rid of them if they are false positives?

[sarabala1979]

@black-snow Do you like to contribute? It is a good first issue

[tooptoop4]

@black-snow the surrounding logs can help to know which line to change

[black-snow]

@sarabala1979 absolutely. Sounds like @isubasinghe already has a notion of where to look.