Kuperman Sergey

This is exactly what i do: ``` seastranger@W-5CG3503TSZ:~/repos/esm/trident$ tridentctl -n trident import volume fs-04c800c498b492990-economy trident_lun_pool_trident_HUUIAUUPCE/trident_pvc_551d8895_a01f_479c_9437_feba9edca656 -f ws/ws-w2yn2-pvc.yaml Error: error communicating with Trident REST API; Post "http://127.0.0.1:8000/trident/v1/volume/import": EOF command terminated with...

the pvc did not exist, it was created as a result of the tridentctl volume import command, it receives the pvc yaml file (without annot) as param: ``` ws/ws-w2yn2-pvc.yaml apiVersion:...

but i see that the annotation that is created on the PVC does contain both volume and lun: ``` annotations: trident.netapp.io/importBackendUUID: 0591493b-1bfc-43f6-b010-4dae8c28b844 trident.netapp.io/importOriginalName: trident_lun_pool_trident_HUUIAUUPCE/trident_pvc_551d8895_a01f_479c_9437_feba9edca656 trident.netapp.io/notManaged: "false" ``` vol - trident_lun_pool_trident_HUUIAUUPCE...

@NA-Scott i have tried creating PVC with the annotation as you suggest, this does not trigger the import flow output in controller log at all, only the command tridentctl volume...

i saw the following event in the namespace where import is attempted: ``` 0s Normal WaitForFirstConsumer persistentvolumeclaim/workspaces-ws-w2yn2-data waiting for first consumer to be created before binding ``` which makes sense...

no, it does not work, the binding mode only affects if the issue with LUKS format happens immediately, or when trying to attach PVC to the pod. I have tried...