← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1629040] [NEW] Incorrect hyper-v driver capability

 

Public bug reported:

The Hyper-V driver incorrectly enables the
'supports_migrate_to_same_host' capability.

This capability seems to have been introduced having the VMWare cluster
architecture in mind, but it leads to unintended behavior in case of the
HyperV driver.

For this reason, the Hyper-V CI is failing on the test_cold_migration
tempest test, which asserts that the host has changed.

** Affects: compute-hyperv
     Importance: Undecided
         Status: New

** Affects: nova
     Importance: Undecided
     Assignee: Lucian Petrut (petrutlucian94)
         Status: In Progress


** Tags: drivers hyper-v

** Description changed:

  The Hyper-V driver incorrectly enables the
- 'supports_migrate_to_same_host' capability. This capability seems to
- have been introduced having the VMWare cluster architecture in mind, but
- it leads to unintended behavior in case of the HyperV driver.
+ 'supports_migrate_to_same_host' capability.
+ 
+ This capability seems to have been introduced having the VMWare cluster
+ architecture in mind, but it leads to unintended behavior in case of the
+ HyperV driver.
  
  For this reason, the Hyper-V CI is failing on the test_cold_migration
  tempest test, which asserts that the host has changed.

** Also affects: compute-hyperv
   Importance: Undecided
       Status: New

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

Title:
  Incorrect hyper-v driver capability

Status in compute-hyperv:
  New
Status in OpenStack Compute (nova):
  In Progress

Bug description:
  The Hyper-V driver incorrectly enables the
  'supports_migrate_to_same_host' capability.

  This capability seems to have been introduced having the VMWare
  cluster architecture in mind, but it leads to unintended behavior in
  case of the HyperV driver.

  For this reason, the Hyper-V CI is failing on the test_cold_migration
  tempest test, which asserts that the host has changed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compute-hyperv/+bug/1629040/+subscriptions


Follow ups