iscsi targets for pvc set on the wrong portal group

Hi, I’m experiencing some weird behavior with the iscsi claims. Nfs works great. set up :

• kubernetes 1.20.2
• runtime : crio
• os : debian 10
• 2 network interfaces, 1 for services, 1 to access storage backend
• iscsi portals on TrueNAS Core 12.0-U2
• Created a 2nd portal for PVCs.

democratic-csi is installed using the command helm upgrade --install --create-namespace --values truenas-iscsi.yml -- namespace democratic-csi truenas-iscsi democratic-csi/democratic-csi truenas-iscsi.yml.txt

When deploying a test pod using a pvc of this class, the pvc is created correctly, but the pod can’t bind to it. output.txt Here is the pod definition : test-pod.yml.txt

The zvol is created on truenas and the initiator is created too. The problem is that the portalgroup defined in the target is not the one I defined for democratic. 1 instead of 2 in this screenshot.

When I manually change the portal group to 2 in the target’s configuration on truenas, the pod is able to bind on the pv and the container creation can continue successfully.

I’m not sure if it’s an issue in my config, democratic-csi or the truenas api…

Thank you for any help for making this driver work correctly in this setup.

[infra-monkey]

True they made a big deal with the new ui and api stuff, i thought it was flawless. But still humans behind the whole thing. Thanks again and keep on the great work. I’ll close this issue

[travisghansen]

@monkey-b I’ll bring it up with the iX team. I honestly only thought that was an issue with the old UI, I was under the impression the fancy new UI was showing the actual ID or I could have pinpointed sooner 😦