yahoo-eng-team team mailing list archive

[Jay Bryant <jsbryant@xxxxxxxxxx>]

Correction, as I looked at bug #1221525 they are two separate issues.  I
will be checking in the fix that the storwize_svc driver needs against
this bug while I work on resolving the other bug.

** This bug is no longer a duplicate of bug 1221525
   Cannot attach a volume to a Hyper-V Nova instance with a Storwize v7000 target

** Project changed: nova => cinder

** Changed in: cinder
       Status: New => Confirmed

** Changed in: cinder
   Importance: Undecided => Critical

** Changed in: cinder
     Assignee: (unassigned) => Jay Bryant (jsbryant)

** Changed in: cinder
    Milestone: None => juno-1

** Tags removed: hyper-v
** Tags added: drivers icehouse-backport-potential storwize

-- 
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/1269915

Title:
  Hyper-V unable to find mounted disks when attaching volume to instance
  on IBM Storwize V7K

Status in Cinder:
  Confirmed

Bug description:
  Steps to create:
  1.) Create and instance, hosted on a Hyper-V system
  2.) Create a new volume that is carved out of IBM Storwize V7K
  3.) Confirm both are available/active
  3.) Attach volume to instance
      $ nova volume-attach ldbragst-instance ldbragst-volume auto

  The following stacktrace was pulled from the nova logs on the hyper-v
  node that hosts the instance.

  [Hyper-V Volume Attach Issue]: Unable to find a mounted disk
  http://paste.openstack.org/show/61387/

  After this happens I can confirm that an iSCSI connection exists and
  is 'Connected' through the iSCSI Initiator. The iqn that it is
  connected to is the same iqn that is in the above stacktrace:
  iqn.1986-03.com.ibm:2145.ngp02-iscsi.node1

  If I don't attempt to clean up anything on the Hyper-V node and don't
  'Disconnect' the Discovered Targets
  (iqn.1986-03.com.ibm:2145.ngp02-iscsi.node1) and run the same exact
  'nova attach-volume' command, I get a different error detailed below:

  [Hyper-V Volume Attach Issue]: WMI Error Code
  http://paste.openstack.org/show/61388/

  Which I believe is being addressed in
  https://bugs.launchpad.net/nova/+bug/1221525 . I just wanted to note
  that it seems to be a side effect of the first issue.

  Here, what I think is happening is that the device_number here
  https://github.com/openstack/nova/blob/master/nova/virt/hyperv/volumeops.py#L87
  doesn't detect that a connection is established, so it tries to
  establish a connection, like the first run, by calling
  https://github.com/openstack/nova/blob/master/nova/virt/hyperv/volumeutilsv2.py#L45
  and fails in this WMI call,
  https://github.com/openstack/nova/blob/master/nova/virt/hyperv/volumeutilsv2.py#L56

  
  Here is some manual testing I did in a Python terminal on the compute node, specifically testing the case here https://github.com/openstack/nova/blob/master/nova/virt/hyperv/basevolumeutils.py#L122
   

  http://paste.openstack.org/show/61389/

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