So just to keep the list updated this was resolved offline by disconnecting the iscsi session (iscsiadm -m session -u), then logging into it again. What probably happened is that there was an existing bad session, and since it's existing, one can't login again. Once logged out, a new good session is created. A bad session can result from a wrong/stale /etc/iscsi/initiatorname.iscsi . The aboce is what should be sone in this case. If there's just a name change, restart iscsid before trying to login. And thank you Nir for your help in helping :) ----- Original Message -----
From: "Nicolas Ecarnot" <nicolas@ecarnot.net> To: users@ovirt.org Sent: Tuesday, October 21, 2014 1:18:47 PM Subject: [ovirt-users] iSCSI connection to a LUN - EMC CX4-120 - Login OK but no LUN
Hi,
Setting up our third oVirt infra, we are now connecting it to an EMC CX4-120 SAN. On this SAN, we have set up a classical storage group, added the authorized hosts, registered them.
On the oVirt side, we want to create the first master storage domain and so we give the GUI the right SAN ip, and the iSCSI connection is working.
We see appearing the two virtual IP of the storage processors (A and B), and the login button reacts well, no error appears. But no LUN shows up at this point.
Looking at the hosts used by this connection, it appears that the iSCSI connection worked well, and that the LUN is visible on the host side ("iscsiadm -m session -P3").
So now, in the web GUI, there is no LUN showing up I could connect to. I have isolated the relevant logs - the engine one and the vdsm one :
Engine : http://pastebin.com/32Sg85C8 VDSM : http://pastebin.com/BbY6mVSk
I don't know what is missing? May you help me?
-- Nicolas Ecarnot _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users