yahoo-eng-team team mailing list archive

[Luis Fernandez <luis.fernandez.alvarez@xxxxxxx>]

Public bug reported:

When an iSCSI volume is attached to Hyper-V, the OS has to refresh the
list of LUNs on the iSCSI target to discover the new one.

The current mechanism implemented only works for the first LUN because
the connection to the target is done after the LUN is exposed to the
hypervisor. The rest of LUNs exposed to the hypervisor hosted in the
same iSCSI target won't be refreshed on time to be discovered by the
machine.

This looks related with the wrong assumption of having one LUN per iscsi
target, but it's also possible to have several LUNs per iscsi target.

The patch for this bug should refresh the list of LUNs when a new
attachment request is received. In our test environment (Hyper-V 2012
R2), a WMI call like the following one helped to solve this issue:

self._conn_storage.query("SELECT * FROM MSFT_iSCSISessionToDisk")

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: hyper-v iscsi volumes

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1372823

Title:
  iSCSI LUN list not refreshed in Hyper-V 2012 R2 compute nodes

Status in OpenStack Compute (Nova):
  New

Bug description:
  When an iSCSI volume is attached to Hyper-V, the OS has to refresh the
  list of LUNs on the iSCSI target to discover the new one.

  The current mechanism implemented only works for the first LUN because
  the connection to the target is done after the LUN is exposed to the
  hypervisor. The rest of LUNs exposed to the hypervisor hosted in the
  same iSCSI target won't be refreshed on time to be discovered by the
  machine.

  This looks related with the wrong assumption of having one LUN per
  iscsi target, but it's also possible to have several LUNs per iscsi
  target.

  The patch for this bug should refresh the list of LUNs when a new
  attachment request is received. In our test environment (Hyper-V 2012
  R2), a WMI call like the following one helped to solve this issue:

  self._conn_storage.query("SELECT * FROM MSFT_iSCSISessionToDisk")

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1372823/+subscriptions