You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
My large workflow failed when encounter "invalid connection", Because my cluster has been working fine, this is an occasional problem.
We should retry when offload info encounters this error.
Version(s)
latest
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.
time="2024-09-09T13:24:51.702Z" level=warning msg="Non-transient error: invalid connection"31605 time="2024-09-09T13:24:51.702Z" level=warning msg="Failed to dehydrate: workflow is longer than maximum allowed size. compressed size 1113230 > maxSize 1048576Tried to of fload but encountered error: invalid connection" namespace=default workflow=large-workflow-t696s31606 time="2024-09-09T13:24:51.703Z" level=info msg="cleaning up pod" action=deletePod key=default/large-workflow-t696s-sleep-545703870/deletePod31607 time="2024-09-09T13:24:51.705Z" level=info msg="Updated phase Running -> Error" namespace=default workflow=large-workflow-t696s31608 time="2024-09-09T13:24:51.705Z" level=info msg="Updated message -> workflow is longer than maximum allowed size. compressed size 1113230 > maxSize 1048576Tried to offloa d but encountered error: invalid connection" namespace=default workflow=large-workflow-t696s
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?
My large workflow failed when encounter "invalid connection", Because my cluster has been working fine, this is an occasional problem.
We should retry when offload info encounters this error.
Version(s)
latest
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
The text was updated successfully, but these errors were encountered: