yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => Fix Released

** Changed in: neutron
    Milestone: None => icehouse-2

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

Title:
  somehow getting duplicate openvswitch agents for the same host

Status in OpenStack Neutron (virtual network service):
  Fix Released
Status in tripleo - openstack on openstack:
  In Progress

Bug description:
  While investigating spurious failures in our TripleO continous
  deployment, I had this problem:

  +--------------------------------------+--------------------+-------------------------------------+-------+----------------+
  | id                                   | agent_type         | host                                | alive | admin_state_up |
  +--------------------------------------+--------------------+-------------------------------------+-------+----------------+
  | 3a9c6aca-e91f-49c9-850a-67db219fdf58 | L3 agent           | overcloud-notcompute-wjo2jbvvd2sm   | :-)   | True           |
  | 3fb9f6cf-b545-4a34-a490-dda834973d1e | Open vSwitch agent | overcloud-novacompute0-ubrjpv4jz64a | xxx   | True           |
  | 855349b2-b0fc-4270-bb96-385b61aa5a6c | DHCP agent         | overcloud-notcompute-wjo2jbvvd2sm   | :-)   | True           |
  | 8b8a4128-9716-42ee-b886-f053db166ce3 | Metadata agent     | overcloud-notcompute-wjo2jbvvd2sm   | :-)   | True           |
  | c8297e0d-8575-47f0-ae65-499c1e0319b3 | Open vSwitch agent | overcloud-notcompute-wjo2jbvvd2sm   | :-)   | True           |
  | f746fc1d-9083-46f4-a922-739c5d332d7c | Open vSwitch agent | overcloud-novacompute0-ubrjpv4jz64a | xxx   | True           |
  +--------------------------------------+--------------------+-------------------------------------+-------+----------------+

  Note that overcloud-novacompute0-ubrjpv4jz64a has _two_ Open vSwitch
  agents.

  This caused many 'vif_type=binding_failed' errors when booting nova
  instances.

  Deleting f746fc1d-9083-46f4-a922-739c5d332d7c resulted in the problem
  going away.

  Seems like there might be a race if the agent restarts quickly, thus
  not seeing its own agent record and sending a second RPC to create
  one. I think, I am not entirely sure how this works, that is just a
  hypothesis.

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