yahoo-eng-team team mailing list archive

[Simon Pasquier <simon.pasquier@xxxxxxxx>]

Public bug reported:

The nova-event-callback blueprint [1] implemented the notifications of
active/down ports to Nova. Before effectively starting an instance, Nova
compute waits for a "VIF plugged" notification from Neutron.

I'm running ODL ML2 driver in a devstack using the master branch and I
notice that the ODL driver doesn't notify back the Nova API. Hence with
the default settings, the VM creation always fails.

As a workaround, set the following parameters in your nova.conf:
vif_plugging_timeout = 10
vif_plugging_is_fatal = False

With this configuration, I'm able to boot and connect to the instances
but the Neutron ports are always reported as DOWN [2].

[1] https://blueprints.launchpad.net/neutron/+spec/nova-event-callback
[2] http://paste.openstack.org/show/74861/

** Affects: neutron
     Importance: Undecided
         Status: New

** Summary changed:

- ODL ML2 driver doesn't notify active ports 
+ ODL ML2 driver doesn't notify active/inactive ports

** Description changed:

  The nova-event-callback blueprint [1] implemented the notifications of
  active/down ports to Nova. Before effectively starting an instance, Nova
  compute waits for a "VIF plugged" notification from Neutron.
  
  I'm running ODL ML2 driver in a devstack using the master branch and I
  notice that the ODL driver doesn't notify back the Nova API. Hence with
  the default settings, the VM creation always fails.
  
  As a workaround, set the following parameters in your nova.conf:
  vif_plugging_timeout = 10
  vif_plugging_is_fatal = False
  
- And your instances will boot successfully.
+ With this configuration, I'm able to boot and connect to the instances
+ but the Neutron ports are always reported as DOWN [2].
  
  [1] https://blueprints.launchpad.net/neutron/+spec/nova-event-callback
+ [2] http://paste.openstack.org/show/74861/

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1301449

Title:
  ODL ML2 driver doesn't notify active/inactive ports

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  The nova-event-callback blueprint [1] implemented the notifications of
  active/down ports to Nova. Before effectively starting an instance,
  Nova compute waits for a "VIF plugged" notification from Neutron.

  I'm running ODL ML2 driver in a devstack using the master branch and I
  notice that the ODL driver doesn't notify back the Nova API. Hence
  with the default settings, the VM creation always fails.

  As a workaround, set the following parameters in your nova.conf:
  vif_plugging_timeout = 10
  vif_plugging_is_fatal = False

  With this configuration, I'm able to boot and connect to the instances
  but the Neutron ports are always reported as DOWN [2].

  [1] https://blueprints.launchpad.net/neutron/+spec/nova-event-callback
  [2] http://paste.openstack.org/show/74861/

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