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 => kilo-1

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

Title:
  When two ovs ports contain same external_ids:face-id field, ovs agent
  might fail finding correct port.

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:
  As the title says, if there are 2 different ovs ports with the same
  external_ids:iface-id field (which is the port_id), when at least one
  of them is managed by the ovs agent, it might fail finding the correct
  one if they are not connected to the same bridge.

  Steps to reproduce:
  1. Create a router with an internal port to some Neutron network
  2. Find the port in 'ovs-vsctl show'
  3. Use the following command to find the port_id in ovs: sudo ovs-vsctl  --columns=external_ids list Interface <port_name>
  4. Use the following commands to create a new port with the same field in a new bridge:
   sudo ovs-vsctl add-br a
   sudo ip link add dummy12312312 type dummy
   sudo ovs-vsctl add-port br-a dummy12312312
   sudo ovs-vsctl set Interface dummy12312312 external_ids:iface-id="<port_id>" # port_id was obtained in point 3.
  5. Restart the ovs agent.

  At this point the ovs agent's log should show "Port: dummy12312312 is
  on br-a, not on br-int".

  Expected result: ovs agent should know to iterate though the options
  and find the correct port in the correct bridge.

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