yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
       Status: Confirmed => Expired

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

Title:
  Multipath device descriptor and iscsi device not deleted when
  detaching multiple volumes at the same time at the same host

Status in OpenStack Compute (nova):
  Expired

Bug description:
  For every detached volume the nova-compute instance deletes all multipath devices from the host while detaching. This is working fine if the volumes are detached each by each, but not for multiple detachment.
  Nova-compute always rescans the iscsi devices before it detaches them. The rescan reconnects all missing devices if the Volume is still available on the VNX. In the time between the iscsi devices are deleted and cinder-volume is actually detaching the volume on the vnx site, the iscsi connections will be always reconnected by any rescan. All detachments run into one thread on the host, so the detachment is done one by one. However the detachment on the cinder-volume site is done through multithreading and the nova-compute is not waiting between the detachments for cinder-volume to detach. So it can happen that the device is deleted and the next detachment of the next volume brings back the devices.
  The next time a volume is attached to this VM on this host an error will occur. Or if this is working the the volume will stay in use until the VM is terminated. It is not possible to detach the volume again.
  Also the information of the volume is not updated for the second detachment. The size stays the same also the new attachment is totally different.

  
  3600601604781340063b2b4293601e411 dm-2 DGC     ,VRAID
  size=4.0G features='0' hwhandler='0' wp=rw
  |-+- policy='round-robin 0' prio=2 status=enabled
  | |- 7:0:0:3 sdr  65:16  failed ready  running
  | `- 6:0:0:3 sdq  65:0   failed ready  running
  `-+- policy='round-robin 0' prio=1 status=enabled
    `- 9:0:0:3 sds  65:32  failed ready  running

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