https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# longhorn-storage
a
This message was deleted.
q
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?
n
Hi @quick-sandwich-76600
I think the issue is the volumes are stuck in a loop trying to attach/detach to worker nodes. I see this is a bug reported in 1.2.4 and addressed in 1.2.5
q
But you are installing the latest version (1.3.1), is that right?
n
No I am using 1.2.4 and I see 1.2.5 is the latest from here - https://github.com/longhorn/longhorn/releases
q
Out of curiosity .... why do you use the old version?
n
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
q
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.
n
I am unable to find the 1.3.1 version. can you please share the latest release url?
q
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.
n
Thanks much @quick-sandwich-76600 for the info
I have another doubt...I see that 1.2.5 is the latest released version
c
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.
tl;dr use the highest version, not the newest
n
Thanks @creamy-pencil-82913 I will go with 1.2.5 then and see if the issue still persists
c
that’s not what I was suggesting at all but ok
s
Ok in your new cluster does it have the iscsi package? ( I can't remember the full title of the package).
15 Views
Open in Slack
PreviousNext
Powered by