[ovirt-users] iSCSI question... LUNS->Targets balnk

[Jiri Belka]

> From: "Alan Murrell" <lists at murrell.ca>
> To: users at ovirt.org
> Sent: Thursday, August 6, 2015 7:54:06 PM
> Subject: [ovirt-users] iSCSI question... LUNS->Targets balnk
> 
> Hello,
> 
> I am hoping someone here has had experience in setting up an iSCSI
> target using 'targetcli'.   I followed the following guide:
> <http://www.certdepot.net/rhel7-configure-iscsi-target-initiator-persistently/>.
> This is on my single host (with hosted engine currently running; I am using
> a seperate HDD for the iSCSI
> storage)
> 
> The iSCSI initiator of my host, from it's information page in oVirt,
> is <iqn.1994-05.com.redhat:ba4cc8b3368e>, so I created an ACL with
> that name.  Here is a result of the listing in the 'acls' directory
> for my IQN:
> 
> --- START ---
> /iscsi/iqn.20...gt1/tpg1/acls> ls
> o- acls ..............................................................
> [ACLs: 1]
>    o- iqn.1994-05.com.redhat:ba4cc8b3368e ......................
> [Mapped LUNs: 1]
>    | o- mapped_lun0 .................................... [lun0
> block/block1 (rw)]
> --- END ---
> 
> So it appears as though my host's initiator is mapped to my LUN 0.
> 
> When I go in to oVirt and add iSCSI storage, the "Discover" finds my
> target, and I can even log in successfully, however when I click on
> the "LUNS->Targets" side tab, there are no LUNs listed, so I cannot
> add any iSCSI storage.
> 
> Any ideas on why the LUN is not showing up?

Have you tried to attach LUN on anything else then oVirt?
This way you could find out if it is oVirt or a general issue.

j.