Reviewed: https://review.openstack.org/372423
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=19f3e9a50edcd4027a325aaf60c6e5fbedd7baac
Submitter: Jenkins
Branch: master
commit 19f3e9a50edcd4027a325aaf60c6e5fbedd7baac
Author: Kevin Benton <ke...@benton.pub>
Date: Mon Sep 19 04:21:27 2016 -0700
Fix linuxbridge trunk subport RPC event handler
The part of the linuxbridge trunk driver that actually triggered
the dataplane wiring for subport changes was incorrectly trying to
fetch the trunk using the trunk ID with a method expecting the port
ID. This would always result in it thinking the trunk wasn't on the
host and returning without wiring.
This fixes it by adding another method to fetch trunks by trunk ID.
All of the other operations in this function already expect trunk IDs.
This was discovered and the fix verified with the scenario test in
the dependent patch.
Change-Id: I25324bc1445cc083799ff54f8508a9505517ce84
Closes-Bug: #1625136
** Changed in: neutron
Status: In Progress => 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/1625136
Title:
linuxbridge trunk plugin doesn't handle subport changes without trunk
update
Status in neutron:
Fix Released
Bug description:
The subport event handler is not correctly triggering wiring changes
when the subports for a trunk already present on the agent are
changed. This leaves a trunk dataplane frozen in time once its first
wired up on the linux bridge agent unless it receives another trunk
event.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1625136/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
