yahoo-eng-team team mailing list archive

[Lucian Petrut <lpetrut@xxxxxxxxxxxxxxxxxxxxxx>]

Public bug reported:

When using OVS, the Hyper-V driver creates the OVS ports only after the
instance is powered on (due to a Hyper-V limitation).

The issue is that in case of cold migrations/resize, this step is currently skipped, as the driver doesn't pass the network info object when powering on the instance:
https://github.com/openstack/nova/blob/07b6580a1648a860eefb5a949cb443c2a335a89a/nova/virt/hyperv/migrationops.py#L300-L301

Simply passing that object will fix the issue.

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

** Affects: nova
     Importance: Undecided
         Status: New

** 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/1657424

Title:
  Hyper-V: Instance ports not bound after resize

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

Bug description:
  When using OVS, the Hyper-V driver creates the OVS ports only after
  the instance is powered on (due to a Hyper-V limitation).

  The issue is that in case of cold migrations/resize, this step is currently skipped, as the driver doesn't pass the network info object when powering on the instance:
  https://github.com/openstack/nova/blob/07b6580a1648a860eefb5a949cb443c2a335a89a/nova/virt/hyperv/migrationops.py#L300-L301

  Simply passing that object will fix the issue.

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