<div dir="ltr"><div><div>The test disks are not attached to any virtual machine. nothing done on the hosts.<br> I just saw that the all test LUNs are still logged into target side so I
went to the host(it was in the maintenance ) all disks are still there.<br><br>I just managing everything over the web gui: <br>Select host as SPM, then disks->new->directLUN-><wbr>discovertargets->login->ok<br></div><div>on the host the disks are visible.<br></div><div>iscsiadm -m session -o show<br>tcp: [6] <a href="http://10.10.10.35:3260" target="_blank">10.10.10.35:3260</a>,1 iqn.2003-01.org.linux-iscsi.<wbr>c1701.x8664:sn.5b791971cd78 (non-flash)<br><br></div><div>Putting host to maintenance:<br></div><div>the disks are still there:<br>lsscsi<br>[0:0:0:0] disk ATA ST3500630NS K /dev/sda <br>[11:0:0:0] disk LIO-ORG c1701iser 4.0 /dev/sdb <br>[11:0:0:1] disk LIO-ORG c1701iser32k 4.0 /dev/sdc <br><br></div>activating deactivating the host does not change situation.<br></div><div>I dont see any attempt of vdsm to logout the disks. I can see in the vdsmd.logs that "[storage.Mount] unmounting /rhev/data-center/mnt/......" unmounting the nfs part but nothing from [storage.ISCSI] <br></div><div><br></div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 16, 2017 at 4:25 PM, Nir Soffer <span dir="ltr"><<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, Feb 16, 2017 at 5:13 PM, Arman Khalatyan <<a href="mailto:arm2arm@gmail.com">arm2arm@gmail.com</a>> wrote:<br>
> Hi,<br>
> In ovirt 4.1 when I put the host into maintenance mode then the nfs mounts<br>
> are unmounted as expected.<br>
> but the hosts are still logged into the targets.<br>
><br>
> Is it expected behavior?? If yes what is the use of it?<br>
<br>
</span>No, if ovirt connected to the target, it should disconnect from the target.<br>
<br>
Maybe you connected manually to the target before that?<br>
<br>
A good test to verify this would be to do this in maintenance mode:<br>
<br>
iscsiadm -m node -o delete<br>
<br>
Then activate and deactivate the host several times, and check that<br>
no iscsi session are active when host enter maintenance.<br>
<span class=""><br>
> Another thing concerning to the permanently removed direct LUNs.<br>
> They are still in the /var/lib/iscsi/nodes and /var/lib/iscsi/send_targets/*<br>
> Would be good to cleanup the folders if users are removing permanently the<br>
> LUNs.<br>
<br>
</span>We don't manage the LUNs - if you are removing the LUNs manually, and<br>
the target providing this LUNs is not needed any more, you are responsible<br>
for removing the nodes from iscsi database.<br>
<br>
I don't think we are removing nodes and targets from a host, only updating<br>
them when you connect to a server. We also don't have a way to remove<br>
a target from engine database, so engine cannot ask vdsm to remove targets.<br>
<span class="HOEnZb"><font color="#888888"><br>
Nir<br>
</font></span></blockquote></div><br></div>