yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1260440@xxxxxxxxxxxxxxxxxx>]

** Changed in: neutron
       Status: Incomplete => Invalid

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

Title:
  nova-compute host is added to scheduling pool before Neutron can bind
  network ports on said host

Status in neutron:
  Invalid
Status in OpenStack Compute (nova):
  Expired
Status in tripleo:
  Fix Released

Bug description:
  This is a race condition.

  Given a cloud with 0 compute nodes available, on a compute node:
  * Start up neutron-openvswitch-agent
  * Start up nova-compute
  * nova boot an instance

  Scenario 1:
  * neutron-openvswitch-agent registers with Neutron before nova tries to boot instance
  * port is bound to agent
  * instance boots with correct networking

  Scenario 2:
  * nova schedules instance to host before neutron-openvswitch-agent is registered with Neutron
  * nova instance fails with vif_type=binding_failed
  * instance is in ERROR state

  I would expect that Nova would not try to schedule instances on
  compute hosts that are not ready.

  Please also see this mailing list thread for more info:

  http://lists.openstack.org/pipermail/openstack-
  dev/2013-December/022084.html

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