Hi Vered,
Le 22/10/2014 09:40, Vered Volansky a écrit :
Hi,
Please attach send the full engine and vdsm logs to the list.
Here they are (I don't know if they will be authorized?)
Also - what version are you using.
Is this an upgrade? If so - which versions?
This is a clean new install.
[root@serv-mvm-adms01 tmp]# rpm -qa|grep -i virt
ovirt-engine-lib-3.4.4-1.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-3.4.4-1.el6.noarch
ovirt-engine-setup-3.4.4-1.el6.noarch
ovirt-engine-backend-3.4.3-1.el6.noarch
ovirt-engine-dbscripts-3.4.3-1.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-3.4.4-1.el6.noarch
ovirt-engine-websocket-proxy-3.4.4-1.el6.noarch
ovirt-iso-uploader-3.4.4-1.el6.noarch
ovirt-release34-1.0.3-1.noarch
ovirt-engine-webadmin-portal-3.4.3-1.el6.noarch
ovirt-engine-sdk-python-3.4.4.0-1.el6.noarch
ovirt-host-deploy-1.2.3-1.el6.noarch
ovirt-host-deploy-java-1.2.3-1.el6.noarch
ovirt-image-uploader-3.4.3-1.el6.noarch
ovirt-engine-cli-3.4.0.5-1.el6.noarch
ovirt-engine-tools-3.4.3-1.el6.noarch
ovirt-engine-3.4.3-1.el6.noarch
ovirt-engine-setup-base-3.4.4-1.el6.noarch
ovirt-engine-setup-plugin-websocket-proxy-3.4.4-1.el6.noarch
ovirt-engine-restapi-3.4.3-1.el6.noarch
ovirt-engine-userportal-3.4.3-1.el6.noarch
[root@serv-vm-adms02 tmp]# rpm -qa|grep -i virt
libvirt-python-0.10.2-29.el6_5.12.x86_64
libvirt-client-0.10.2-29.el6_5.12.x86_64
libvirt-0.10.2-29.el6_5.12.x86_64
libvirt-lock-sanlock-0.10.2-29.el6_5.12.x86_64
ovirt-release34-1.0.3-1.noarch
--
Nicolas Ecarnot
Vered
----- Original Message -----
> From: "Nicolas Ecarnot" <nicolas(a)ecarnot.net>
> To: users(a)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(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>
--
Nicolas Ecarnot