Hyper-V won't disconnect iSCSI targets created by tgt

[Lucian Petrut]

When detaching volumes, the Hyper-V driver decides whether the iSCSI target should be disconnected or not by comparing the number of volumes being disconnected and the total number of available LUNs of the according iSCSI target.

This causes problems as TGT exports one extra reserved LUN. For this reason, the according iSCSI targets won't be disconnected when a volume exported by TGT is detached.

The fix consists in checking the disk types when counting the available LUNs of a target.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/136433

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/136433
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=16484eca967c8d3c1a194362e8d1d6d87a711983
Submitter: Jenkins
Branch: master

commit 16484eca967c8d3c1a194362e8d1d6d87a711983
Author: Lucian Petrut <email address hidden>
Date: Fri Nov 21 19:17:31 2014 +0200

    Hyper-V: fix tgt iSCSI targets disconnect issue

    When detaching volumes, the Hyper-V driver decides whether the
    iSCSI target should be disconnected or not by comparing the number
    of volumes being disconnected and the total number of available LUNs
    of the according iSCSI target.

    This causes problems as tgt exports one extra reserved LUN. For
    this reason, the according iSCSI target won't be disconnected
    when a volume exported by TGT is detached.

    The fix consists in checking the disk types when counting the
    available LUNs of a target.

    Change-Id: I0c2a723b94dae5b1c3838b9644537324606128e5
    Closes-Bug: #1395063