argo-workflows/walk-through/volumes/

[giscus[bot]]

argo-workflows/walk-through/volumes/

https://argoproj.github.io/argo-workflows/walk-through/volumes/

[hxlee309]

Hi, when I run the second workflow, I got the following error:

Name:                volumes-existing-kzzj6
Namespace:           argo
ServiceAccount:      unset (will run with the default ServiceAccount)
Status:              Running
Conditions:          
 PodRunning          False
Created:             Wed Aug 31 02:04:58 -0700 (4 minutes ago)
Started:             Wed Aug 31 02:04:58 -0700 (4 minutes ago)
Duration:            4 minutes 41 seconds
Progress:            0/1

STEP                       TEMPLATE                  PODNAME                           DURATION  MESSAGE
 ● volumes-existing-kzzj6  volumes-existing-example                                                                                                                                                                                                                                
 └───◷ generate            whalesay                  volumes-existing-kzzj6-121436793  4m        Unschedulable: 0/1 nodes are available: 1 persistentvolumeclaim "my-existing-volume" not found. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.  

This workflow does not have security context set. You can run your workflow pods more securely by setting it.
Learn more at https://argoproj.github.io/argo-workflows/workflow-pod-security-context/

[hxlee309]

When I run the third workflow, I got the following error:

Name:                template-level-volume-66tbm
Namespace:           argo
ServiceAccount:      unset (will run with the default ServiceAccount)
Status:              Failed
Message:             child 'template-level-volume-66tbm-3589372903' failed
Conditions:          
 PodRunning          False
 Completed           True
Created:             Wed Aug 31 02:14:17 -0700 (21 seconds ago)
Started:             Wed Aug 31 02:14:18 -0700 (20 seconds ago)
Finished:            Wed Aug 31 02:14:38 -0700 (now)
Duration:            20 seconds
Progress:            0/1
ResourcesDuration:   1s*(1 cpu),1s*(100Mi memory)

STEP                            TEMPLATE                 PODNAME                                 DURATION  MESSAGE
 ✖ template-level-volume-66tbm  generate-and-use-volume                                                    child 'template-level-volume-66tbm-3589372903' failed                                                                                                                                                                                                                                
 └───✖ generate-volume          generate-volume          template-level-volume-66tbm-3589372903  8s        Error (exit code 1): no more retries Error from server (Forbidden): error when creating "/tmp/manifest.yaml": persistentvolumeclaims is forbidden: User "system:serviceaccount:argo:default" cannot create resource "persistentvolumeclaims" in API group "" in the namespace "argo"  

This workflow does not have security context set. You can run your workflow pods more securely by setting it.
Learn more at https://argoproj.github.io/argo-workflows/workflow-pod-security-context/

[tico24]

This makes perfect sense. You need to apply the appropriate rbac to your serviceaccount to allow it to create a volume.

[gocpplua]

When I run the third workflow, I got the following error:

Warning  FailedScheduling  4m44s  default-scheduler  running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition

[winnielinn]

I also have this problem...did your fix it?