12:54 p.m.
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-persisten...;.
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?
Thanks! :-)
Regards,
Alan
1:33 p.m.
New subject: iSCSI question... LUNS->Targets blank
As an update... I was able to connect to the iSCSI target on my host
from a Windows 7 PC on the same network with problem. This was after
I added an ACL for my Win7 PC's IQN.
Not sure if I am missing something in oVirt itself?
Regards,
Alan
11:33 a.m.
I cleared my iSCSI config and ran through the setup again. Once
again, I am able to connect to it the LUN from my Win7 PC, but not
from oVirt.
oVirt is able to discover the target, but when I click "Login", which
is does successfully, there are no LUNs displayed.
Do I need to install something else on my oVirt host? I have been
assuming that oVirt has it's own iSCSI Initiator, but maybe I need to
install one?
-Alan
11:57 a.m.
What does the engine log say, how about the vdsm logs?
go into your host that you have selected to do the iscsi mount and do a
tail -f /var/log/vdsm/vdsm.log
Then then go through the connect sequence. You should get a better idea.
Did you put any acls on the iscsi mount to allow the hosts to connect?
On Aug 10, 2015 12:36 PM, "Alan Murrell" <lists(a)murrell.ca> wrote:
12:18 p.m.
Quoting "Donny Davis" <donny(a)cloudspin.me>:
tail -f /var/log/vdsm/vdsm.log
Then then go through the connect sequence. You should get a better idea.
It shows a successful connect, but keeps trying to do a scan. About
every 30 seconds, the following entry shows up:
--- START ---
Thread-12294::DEBUG::2015-08-10
10:13:09,286::misc::741::Storage.SamplingMethod::(__call__) Trying to
enter sampling method (storage.iscsi.rescan)
Thread-12294::DEBUG::2015-08-10
10:13:09,286::iscsi::424::Storage.ISCSI::(rescan) Performing SCSI
scan, this will take up to 30 seconds
Thread-12294::DEBUG::2015-08-10
10:13:09,286::iscsiadm::97::Storage.Misc.excCmd::(_runCmd)
/usr/bin/sudo -n /sbin/iscsiadm -m session -R (cwd None)
--- END ---
so it seems it never quite finished the scan.
Did you put any acls on the iscsi mount to allow the hosts to
connect?
I did. I was able to get my oVirt host's iSCSI Initiator Name from
it's "General" tab/page "System > Hosts", and created the ACL
for it
in "targetcli":
-- START ---
cd
/iscsi/iqn.2003-01.org.linux-iscsi.yvr001svr01.x8664:sn.33a56c3324e0/tpg1/acls
create iqn.1994-05.com.redhat:ba4cc8b3368e
--- END ---
The output indicated that the ACL was created and mapped to LUN 0. I
ran the exact same command for my Win 7 PC (using it's iSCSI Initiator
Name, of course).
I did not setup any sort of CHAP authentication.
There is one thing I have noticed in viewing my /var/log/messages on
my host/storage that may have an effect. As you may or may not know,
I am running a single-server with hosted engine. My storage is also
on this server.
What I have noticed is that my host/storage server is mounting the
iSCSI target automatically as '/dev/sdd', so I am not sure if that may
be affecting oVirt's ability to scan, if it is already connected to by
the very same host?
(I hope this makes sense? If not, let me know and I can try to answer
your questions better)
1:11 p.m.
Quoting "Donny Davis" <donny(a)cloudspin.me>:
I think you nailed it. There are no disks available to mount. They
are
already mounted to the host.
OK, I will see if I can stop the host itself from mounting the iSCSI
LUN, and then try again through oVirt.
The iSCSI Initiator Name ("IQN"?) I got via the oVirt interface, that
would be the same identifier for the iSCSI client/initiator on the
host itself, right (outside of oVirt, I mean)?
Regards,
Alan
12:41 a.m.
I think it is something with oVirt. I installed a VM with FreeNAS and
configured it tot he setup guide for iSCSI. Once again, I can connect
my Windows 7 PC to the iSCSI target and LUN no problem, but when I try
to add iSCSI storage in oVirt, it sees the target, can log in to the
target but does not see any LUNs.
iSCSI is not a huge deal; I guess I will just stick with NFS and
consider iSCSI in oVirt not ready.
Regards,
Alan
7:24 a.m.
Hi Alan,
basically, it could be that your ACL in your iSCSI server might be configured without the
Initiator IQN of your Host.
do you have any access to your iSCSI server?
also, can u try to connect to the iSCSI server directly from your Host and see if it
works:
1) First discover the targets:
iscsiadm -m discovery -t st -p {scsi_server_ip},{port}
2) Try to log out from the target you were trying to login before:
Example:
iscsiadm -m node -u -T {iqn.2015-07.com.target_name.redhat}:{port} -p
{scsi_server_ip},{port} -u
3) list your files at /sys/block
4) logging in to the target:
iscsiadm -m node -T {iqn.2015-07.com.target_name.redhat}:{port} -p
{scsi_server_ip},{port} -l
5) list again all your files at /sys/block, and check if there were new added block
devices.
Regards,
Maor
----- Original Message -----
3:54 p.m.
Hi Maor,
It is/was probably something really weird with my
single-server/self-hosted engine. As a test I was able to install oVirt
Node 3.5 on another machine that I could borrow for a short period, and
I was able to get it connected via iSCSI to my FreeNAS VM, so I am
satisfied (for my own info) that iSCSI connectivity does work (I didn't
*really* doubt it since others are using it; I was just a bit frustrated
on my last post)
That being said, I think there is something odd/weird when trying to use
iSCSI on a single server/self-hosted engine setup, from which the iSCSI
connection is also being served from (even from a VM)
In the case of the FreeNAS test, I had the "initiator" set to "ALL",
meaning any and all IQNs would be allowed to connect. I didn;t do
anything different on the FreeNAS side of things, and the oVirt 3.5 Node
that I installed was able to connect without any issue whatsoever.
I will try the steps you suggest if/when I ever decide to try this
again, but probably for a setup such as what I am testing, I will
probably stick to the "local" NFS storage (not yet sure if I will go
with or without gluster; doing so sort of gives me more felxability in
the future)
Regards,
Alan
On 16/08/2015 5:24 AM, Maor Lipchuk wrote:
3557
days inactive
3567
days old
11 comments
5 participants
participants (5)
-
Alan Murrell -
Alan Murrell -
Donny Davis -
Jiri Belka -
Maor Lipchuk