← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1627044] [NEW] Last chance call to neutron if VIF plugin notification is lost

 

Public bug reported:

If vif_plugging_is_fatal is set to True (by default) Nova waits to
resume new instance while spawning it. In some cases Neutron
notification is lost (e.g. Rabbitmq issue) and a instance is set to
ERROR state. It happens even if in fact port is ACTIVE on Neutron side
and all should work fine.

This workflow could be improved by calling Neutron before failing.
Nova could check real state of each port in Neutron just before setting the instance in ERROR (if at least one port is not ACTIVE).

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: neutron notification plugging vif

** Description changed:

  If vif_plugging_is_fatal is set to True (by default) Nova waits to
  resume new instance while spawning it. In some cases Neutron
  notification is lost (e.g. Rabbitmq issue) and a instance is set to
  ERROR state. It happens even if in fact port is ACTIVE on Neutron side
  and all should work fine.
  
- This patch improves this workflow. Nova will check real state of each
- port in Neutron just before setting the instance in ERROR (if at least
- one port is not ACTIVE).
+ This workflow could be improved by calling Neutron before failing.
+ Nova could check real state of each port in Neutron just before setting the instance in ERROR (if at least one port is not ACTIVE).

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

Title:
  Last chance call to neutron if VIF plugin notification is lost

Status in OpenStack Compute (nova):
  New

Bug description:
  If vif_plugging_is_fatal is set to True (by default) Nova waits to
  resume new instance while spawning it. In some cases Neutron
  notification is lost (e.g. Rabbitmq issue) and a instance is set to
  ERROR state. It happens even if in fact port is ACTIVE on Neutron side
  and all should work fine.

  This workflow could be improved by calling Neutron before failing.
  Nova could check real state of each port in Neutron just before setting the instance in ERROR (if at least one port is not ACTIVE).

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


Follow ups