yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #10993
[Bug 1283765] Re: ovs plugin changes port it shouldn't change
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1283765
Title:
ovs plugin changes port it shouldn't change
Status in OpenStack Neutron (virtual network service):
Fix Released
Bug description:
(Using ML2 with ovs)
While playing with https://github.com/stackforge/cookbook-openstack-
network/blob/master/files/default/neutron-ha-tool.py to migrate
routers between L3 agents, I had the issue that the connectivity got
lost.
After investigating, it turns out that interface for the port of the
router that is connected to the external network (attached to br-
public -- which is usually named br-ext) gets a tag. Manually removing
the tag makes things work.
I'm attaching a bit of the log where the port_update message is received (it's received for the two interfaces of the router, so this needs some care when reading). We can see the following:
Running command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-vsctl', '--timeout=2', 'set', 'Port', 'qg-923f9b0e-aa', 'tag=2']
However, reading the code, it seems that this kind of actions should
only be done for ports on br-int (because of "vif_port =
self.int_br.get_vif_port_by_id(port['id'])"). So this shouldn't be run
for other ports.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1283765/+subscriptions
References