search

xcp-ng / xenadmin

XCP-ng Center, the Windows management console for XCP-ng and XenServer. /!\ EOL-Notice /!\ Community-maintained only /!\
https://xcp-ng.org
Other
417 stars 71 forks source link

Unable to add iSCSI shared storage to cluster using 7.5 #104

Closed justlikeef closed 5 years ago

justlikeef commented 5 years ago

Describe the bug The only iqn presented once you scan the target is the cluster master, so once added, the lun only connects to the master and auth fails for all other cluster members

To Reproduce

  1. New SR
  2. Select iSCSI, Next
  3. Name, autogenerate, Next
  4. Thin provisioning, Next
  5. Enter target IP, Scan Target Host
  6. Target IQN box has no * iqn

Expected behavior Target IQN box should have an IQN of the base plus *

Additional context Add any other context about the problem here. Hard-/Software involved:

borzel commented 5 years ago

Did you try that with Citrix XenCenter 7.5 or 7.6? Did you try this with the xe-command on CLI? Does it work in XenOrchestra (if possible)?

justlikeef commented 5 years ago

xcp-ng center 7.5. It does work in Xen Orchestra. Did not try the command line.

justlikeef commented 5 years ago

iscsi

cocoon commented 5 years ago

I did some limited test (not finished) with Citrix Xen Center 7.5 + XCP-NG 7.5 + ISCSI and it seems to be the same there.

citrix-xencenter-7 5_thin

So just to make it clear, it only happens if one is selecting GFS2 (THIN).

It seems to be intended (?), have not read much about it, so this is without evidence (manual?), maybe as it is clustered it could be something like single writer using the master over network?

Is this working different with Citrix Xen Server 7.5 + Xen Center 7.5?

olivierlambert commented 5 years ago

FYI, GFS2 is not supported on XCP-ng.

cocoon commented 5 years ago

Ah indeed, I remebered now where you say it, that I read one of your comments about it ... found it: https://github.com/xcp-ng/xcp/issues/49#issuecomment-412835270

"Note that GFS is not supported because XenServer code for it is not open source."

borzel commented 5 years ago

so there is nothing we can do in XCP-ng Center for this :-|

stormi commented 5 years ago

It depends. Maybe there would be a way to not provide functionalities that are known not to work due to them being proprietary. I don't know the feasibility of this, just saying.

borzel commented 5 years ago

hmm... hmm.... I'll try to jump a bit deeper into this ...

borzel commented 5 years ago

https://github.com/xcp-ng/xenadmin/issues/108