[Docs] Docs on synology csi missing isci exntensions being required

[MansM]

Bug Report

https://www.talos.dev/v1.5/kubernetes-guides/configuration/synology-csi/

docs here dont mention anywhere you need the iscsi-tools system extension and how to install them. I kinda figured it out from past experience, but it could be useful to add. The install guide for this is pivoted to openebs, so that need a small revamp to make that work

https://www.talos.dev/v1.5/kubernetes-guides/configuration/replicated-local-storage-with-openebs-jiva/#preparing-the-nodes

Description

Logs

Environment

• Talos version: [talosctl version --nodes <problematic nodes>]
• Kubernetes version: [kubectl version --short]
• Platform:

[plainlystated]

Could you elaborate on this? I'm trying to get the synology CSI stuff working, and hitting a wall. The install went OK, and I can spin up a pod with a PVC. The block device gets auto-created on the synology, but fails to mount the volume into the pod with this error:

Failed in discovery of the target: chroot: can't execute '/usr/bin/env': No such file or directory
GRPC error: rpc error: code = Internal desc = rpc error: code = Internal desc = Failed to login with target iqn [iqn.2000-01.com.synology:nas-5813.pvc-3aefde-3dc6-40b-9c1-7821c4f2f0], err: chroot: can't execute '/usr/bin/env': No such file or directory

Seems like an issue with the created filesystem (have tried ext3 and btrfs), but I'm not sure where to go next. Is this the same error you were having? I did install the extension you mentioned, and tried a slightly older version as well.

[MansM]

Could you elaborate on this? I'm trying to get the synology CSI stuff working, and hitting a wall. The install went OK, and I can spin up a pod with a PVC. The block device gets auto-created on the synology, but fails to mount the volume into the pod with this error:

Failed in discovery of the target: chroot: can't execute '/usr/bin/env': No such file or directory
GRPC error: rpc error: code = Internal desc = rpc error: code = Internal desc = Failed to login with target iqn [iqn.2000-01.com.synology:nas-5813.pvc-3aefde-3dc6-40b-9c1-7821c4f2f0], err: chroot: can't execute '/usr/bin/env': No such file or directory

Seems like an issue with the created filesystem (have tried ext3 and btrfs), but I'm not sure where to go next. Is this the same error you were having? I did install the extension you mentioned, and tried a slightly older version as well.

@plainlystated what is the output of

talosctl get extensions

if no iscsi-tools, follow instructions here on how to installing them: https://www.talos.dev/v1.5/kubernetes-guides/configuration/replicated-local-storage-with-openebs-jiva/#preparing-the-nodes

[mlbiam]

@plainlystated did you ever get synology's csi provider working? I'm getting the exact same error.

@MansM I do have iscsi installed:

talosctl get extensions --nodes 192.168.2.231
NODE            NAMESPACE   TYPE              ID   VERSION   NAME               VERSION
192.168.2.231   runtime     ExtensionStatus   0    1         iscsi-tools        v0.1.4
192.168.2.231   runtime     ExtensionStatus   1    1         util-linux-tools   $VERSION
192.168.2.231   runtime     ExtensionStatus   2    1         schematic          613e1592b2da41ae5e265e8789429f22e121aab91cb4deb6bc3c0b6262961245

and the service is running:

talosctl services --nodes 192.168.2.231
NODE            SERVICE      STATE     HEALTH   LAST CHANGE   LAST EVENT
192.168.2.231   apid         Running   OK       1h1m10s ago   Health check successful
192.168.2.231   containerd   Running   OK       1h2m8s ago    Health check successful
192.168.2.231   cri          Running   OK       1h1m4s ago    Health check successful
192.168.2.231   dashboard    Running   ?        1h1m19s ago   Process Process(["/sbin/dashboard"]) started with PID 2769
192.168.2.231   etcd         Running   OK       1h0m59s ago   Health check successful
192.168.2.231   ext-iscsid   Running   ?        1h1m3s ago    Started task ext-iscsid (PID 3220) for container ext-iscsid
192.168.2.231   ext-tgtd     Running   ?        1h1m4s ago    Started task ext-tgtd (PID 3063) for container ext-tgtd
192.168.2.231   kubelet      Running   OK       1h1m2s ago    Health check successful
192.168.2.231   machined     Running   OK       1h2m12s ago   Health check successful
192.168.2.231   trustd       Running   OK       1h1m4s ago    Health check successful
192.168.2.231   udevd        Running   OK       1h2m11s ago   Health check successful

just as with @plainlystated I can't mount the PVC:

MountVolume.MountDevice failed for volume "pvc-6ed77b15-e921-4e36-bd27-efaf41b1a402" : rpc error: code = Internal desc = rpc error: code = Internal desc = Failed to login with target iqn [iqn.2000-01.com.synology:k8s-nas.pvc-6ed77b15-e921-4e36-bd27-efaf41b1a402], err: chroot: can't execute '/usr/bin/env': No such file or directory (exit status 127)

You're pointing to the OpenEBS instructions, did you need to update the synology CSI to attach to iscsid?

[jdani]

@plainlystated @mlbiam have you solved this somehow? It's happening exactly the same, but using TrueNAS instead of synology

Extensions

NODE             NAMESPACE   TYPE              ID   VERSION   NAME               VERSION
192.168.178.14   runtime     ExtensionStatus   0    1         iscsi-tools        v0.1.4
192.168.178.14   runtime     ExtensionStatus   1    1         util-linux-tools   $VERSION
192.168.178.14   runtime     ExtensionStatus   2    1         schematic          613e1592b2da41ae5e265e8789429f22e121aab91cb4deb6bc3c0b6262961245

Services

NODE             SERVICE      STATE     HEALTH   LAST CHANGE    LAST EVENT
192.168.178.14   apid         Running   OK       2h35m24s ago   Health check successful
192.168.178.14   containerd   Running   OK       2h35m32s ago   Health check successful
192.168.178.14   cri          Running   OK       2h35m29s ago   Health check successful
192.168.178.14   dashboard    Running   ?        2h35m31s ago   Process Process(["/sbin/dashboard"]) started with PID 2086
192.168.178.14   etcd         Running   OK       2h35m24s ago   Health check successful
192.168.178.14   ext-iscsid   Running   ?        2h35m29s ago   Started task ext-iscsid (PID 2397) for container ext-iscsid
192.168.178.14   ext-tgtd     Running   ?        2h35m29s ago   Started task ext-tgtd (PID 2263) for container ext-tgtd
192.168.178.14   kubelet      Running   OK       2h35m27s ago   Health check successful
192.168.178.14   machined     Running   OK       2h35m37s ago   Health check successful
192.168.178.14   syslogd      Running   OK       2h35m36s ago   Health check successful
192.168.178.14   trustd       Running   OK       2h35m24s ago   Health check successful
192.168.178.14   udevd        Running   OK       2h35m33s ago   Health check successful

[mlbiam]

@jdani I did! I don't know about the TueNAS CSI but this is what I did to get it working with Synology - https://github.com/mlbiam/Kargo/blob/main/ISCSI.md