yahoo-eng-team team mailing list archive

[Lucian Petrut <lpetrut@xxxxxxxxxxxxxxxxxxxxxx>]

Nova fix: https://review.openstack.org/#/c/585661/

** Also affects: nova
   Importance: Undecided
       Status: New

** Changed in: nova
       Status: New => In Progress

** Changed in: nova
     Assignee: (unassigned) => Lucian Petrut (petrutlucian94)

** Description changed:

  At the moment, the Hyper-V driver will bind OVS ports only after
  starting the VMs. This is because of an old limitation of the OVS
  Windows port, which has been addressed in OVS 2.5.
  
  This also means that the Nova driver fails when waiting for neutron vif
- plug events[1], since this step is performed later. So users are forced
- to set "vif_plugging_is_fatal", which means that the ports will be down,
- at least for a short time after the instance is reported as ACTIVE. This
- also breaks some Tempest tests.
+ plug events[1], since this step is performed later. So deployers are
+ forced to set "vif_plugging_is_fatal", which means that the ports will
+ be down, at least for a short time after the instance is reported as
+ ACTIVE. This also breaks some Tempest tests.
  
  [1] Trace: http://paste.openstack.org/show/DNKXXMcfqP9KcLY3Da3v/

** Tags added: hyper-v

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

Title:
  Timeout waiting for vif plugging callback for instance

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

Bug description:
  At the moment, the Hyper-V driver will bind OVS ports only after
  starting the VMs. This is because of an old limitation of the OVS
  Windows port, which has been addressed in OVS 2.5.

  This also means that the Nova driver fails when waiting for neutron
  vif plug events[1], since this step is performed later. So deployers
  are forced to set "vif_plugging_is_fatal", which means that the ports
  will be down, at least for a short time after the instance is reported
  as ACTIVE. This also breaks some Tempest tests.

  [1] Trace: http://paste.openstack.org/show/DNKXXMcfqP9KcLY3Da3v/

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