yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1756077] [NEW] Hyper-V: leaked volume connections after live migration

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Lucian Petrut <lpetrut@xxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 15 Mar 2018 13:38:44 -0000
Reply-to: Bug 1756077 <1756077@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

The Hyper-V driver may leak volume connections on the source node side
after performing live migrations if the volume connection info is not
the same among hosts (e.g. different LUN IDs).

One of the affected backends seems to be 3PAR iSCSI, possibly some Dell
iSCSI backends as well.

Fibre Channel backends are not affected as the volume disconnect
operation is a noop in our case.

The Libvirt driver was affected by this issue as well but the initial
fix only targeted the Libvirt driver. A recent commit should fix this
issue for the Hyper-V driver as well, passing the right BDMs when
cleaning up the volume connections on the source node side.

Related bugs:
* https://bugs.launchpad.net/nova/+bug/1475411
* https://bugs.launchpad.net/nova/+bug/1288039

** Affects: nova
     Importance: Undecided
         Status: Fix Committed


** Tags: hyper-v 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/1756077

Title:
  Hyper-V: leaked volume connections after live migration

Status in OpenStack Compute (nova):
  Fix Committed

Bug description:
  The Hyper-V driver may leak volume connections on the source node side
  after performing live migrations if the volume connection info is not
  the same among hosts (e.g. different LUN IDs).

  One of the affected backends seems to be 3PAR iSCSI, possibly some
  Dell iSCSI backends as well.

  Fibre Channel backends are not affected as the volume disconnect
  operation is a noop in our case.

  The Libvirt driver was affected by this issue as well but the initial
  fix only targeted the Libvirt driver. A recent commit should fix this
  issue for the Hyper-V driver as well, passing the right BDMs when
  cleaning up the volume connections on the source node side.

  Related bugs:
  * https://bugs.launchpad.net/nova/+bug/1475411
  * https://bugs.launchpad.net/nova/+bug/1288039

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