In certain cases where multiple ports can have the same
external_ids:iface_id property, the ovs agent will arbitrarily choose
one and ignore the rest. In case the chosen port isn't on the
integration bridge the ovs agent is managing, an error is returned to
the calling function. This is faulty since one of the other ports may
belong to the correct bridge and it should be chosen instead.
This is interesting for future L3 HA integration tests, where 2
different instances of l3 agents are needed to run on the same machine.
In this case, both agents will register ports which have the same
iface_id property, but obviously only one of the ports is relevant for
each agent.
Reviewed: https:/ /review. openstack. org/122357 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=e90d6d6c833 db51964037afd1c 4aa1f521ee380a
Committed: https:/
Submitter: Jenkins
Branch: master
commit e90d6d6c833db51 964037afd1c4aa1 f521ee380a
Author: John Schwarz <email address hidden>
Date: Thu Sep 18 11:24:53 2014 +0300
Iterate over same port_id if more than one exists
In certain cases where multiple ports can have the same ids:iface_ id property, the ovs agent will arbitrarily choose
external_
one and ignore the rest. In case the chosen port isn't on the
integration bridge the ovs agent is managing, an error is returned to
the calling function. This is faulty since one of the other ports may
belong to the correct bridge and it should be chosen instead.
This is interesting for future L3 HA integration tests, where 2
different instances of l3 agents are needed to run on the same machine.
In this case, both agents will register ports which have the same
iface_id property, but obviously only one of the ports is relevant for
each agent.
Closes-bug: #1370914 e51a9ce377fc93a 3f12046b313
Related-bug: #1374947
Change-Id: I05d70417e0f78a