yahoo-eng-team team mailing list archive

[Salvatore Orlando <1338679@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

This has been observed with the VMware NSX plugin, but in theory this
issue might occur with every Neutron plugin when the notifications to
nova are enabled.

In a nutshell the issue is that nova needs to receive a network-vif-
plugged even from neutron in order to be able to boot an instance. On
the other hand in some cases VIF unplug/plug events might be fairly
quick, and thus the neutron side might not be aware at all of the status
change and not send any event.

As a consequence, the instance will not boot even if its VIF are
correctly plugged.

This bug is currently being assigned both neutron and nova because:
- it might deemed a plugin problem. If the plugin is not smart enough to handle VIF plug/unplug notifications than it's not worth using the notification mechanism exposed by nova
- the nova side might add an optional poll mechanism which could run alongside the mechanism waiting for an event and periodically poll neutron to get the VIF status.

** Affects: neutron
     Importance: Undecided
         Status: New

** Affects: nova
     Importance: Undecided
         Status: New

** Also affects: neutron
   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/1338679

Title:
  Some Neutron plugins might miss network-vif-* events

Status in OpenStack Neutron (virtual network service):
  New
Status in OpenStack Compute (Nova):
  New

Bug description:
  This has been observed with the VMware NSX plugin, but in theory this
  issue might occur with every Neutron plugin when the notifications to
  nova are enabled.

  In a nutshell the issue is that nova needs to receive a network-vif-
  plugged even from neutron in order to be able to boot an instance. On
  the other hand in some cases VIF unplug/plug events might be fairly
  quick, and thus the neutron side might not be aware at all of the
  status change and not send any event.

  As a consequence, the instance will not boot even if its VIF are
  correctly plugged.

  This bug is currently being assigned both neutron and nova because:
  - it might deemed a plugin problem. If the plugin is not smart enough to handle VIF plug/unplug notifications than it's not worth using the notification mechanism exposed by nova
  - the nova side might add an optional poll mechanism which could run alongside the mechanism waiting for an event and periodically poll neutron to get the VIF status.

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