Hi, I am using an RKE2 cluster with 1 master node and 5 worker nodes. I have deployed longhorn as a storage class and deployed a mongodb application. Longhorn successfully created the PV and it is bound state as well but the pod is not into Running state because the volume is not attached to any of the worker nodes. Found that "/dev/longhorn" folder is missing in all the worker nodes. Also the "instance-manager" pods are throwing the following error,

[pvc-28f57305-2b5b-44c8-9447-549101dea147-e-ded1735d] time="2022-09-22T10:59:13Z" level=warning msg="FAIL to discover due to Failed to execute: nsenter [--mount=/host/proc/1/ns/mnt --net=/host/proc/1/ns/net iscsiadm -m discovery -t sendtargets -p 10.42.50.26], output , stderr, iscsiadm: Cannot perform discovery. Invalid Initiatorname.\niscsiadm: Could not perform SendTargets discovery: invalid parameter\n, error exit status 7"
[pvc-28f57305-2b5b-44c8-9447-549101dea147-e-ded1735d] time="2022-09-22T10:59:13Z" level=warning msg="Nodes cleaned up for iqn.2019-10.io.longhorn:pvc-28f57305-2b5b-44c8-9447-549101dea147"

I am not sure what I am missing. Any suggestions would be appreciated.

Hi, Seems similar to what is described in this GitHub issue: https://github.com/longhorn/longhorn/issues/4324 May you have a look and try the solution provided there?

Hi @quick-sandwich-76600

But you are installing the latest version (1.3.1), is that right?

No I am using 1.2.4 and I see 1.2.5 is the latest from here - https://github.com/longhorn/longhorn/releases

Out of curiosity .... why do you use the old version?

I have used it some months ago and it worked fine but when I try to use the same in a new cluster now, I am facing this issue

Yes, I get that, but there are a lot of updates on 1.3.1, so if you are starting with a new cluster/deployment, it's better to go for the latest version.

I am unable to find the 1.3.1 version. can you please share the latest release url?

Sure: https://github.com/longhorn/longhorn/releases/tag/v1.3.1 1.2.5 update was the last released version chronologically, so that's why it seems the most recent on GitHub. Sometimes that creates confusion.

Thanks much @quick-sandwich-76600 for the info

like Juan said, GH sorts tags chronologically, not by version. So 1.2.5 is the most recent release, but not the newest from a code perspective.

Thanks @creamy-pencil-82913 I will go with 1.2.5 then and see if the issue still persists

that’s not what I was suggesting at all but ok

Ok in your new cluster does it have the iscsi package? ( I can't remember the full title of the package).