Closed eogns47 closed 2 weeks ago
I just realized that the /mainctrfs
path is a path that can be automatically generated by the Kubernetes cluster when it mounts a specific path as the file system of a container. 😅
It looks like the issue is something other than the path.
I'll close the issue, go back to root cause analysis and create an example workflow, and then reopen the issue.
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 i set the path value like this, the file will not be found because it is prefixed with the path
/mainctrfs
The strangest thing is that this issue doesn't happen every time you run the workflow, but rather periodically for the same template. I think the next issue is a similar phenomenon. https://github.com/argoproj/argo-workflows/issues/5825
Version(s)
v.3.5.8
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