Reviewed: https://review.openstack.org/266114 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2540c84c7624892cd64514a5864731433f3889bb Submitter: Jenkins Branch: master
commit 2540c84c7624892cd64514a5864731433f3889bb Author: Assaf Muller <[email protected]> Date: Mon Jan 11 21:58:30 2016 -0500 Fix regression with unbound ports and l2pop When l2pop is enabled and an unbound port is deleted l2pop mech driver raises an exception as a result of patch: https://review.openstack.org/#/c/263471/ As a result of the same patch, when an unbound port's IP address is changed l2pop sends a fanout RPC message needlessly. Change-Id: Ia81c03dcdf7aef9528c9c2b9527399251fa6aad7 Closes-Bug: #1533013 ** 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/1533013 Title: L2pop raises exception when deleting an unbound port Status in neutron: Fix Released Bug description: Some brilliant individual introduced a regression during a refactor (https://review.openstack.org/#/c/263471/) that causes an exception to be raised when an unbound port is deleted. For example: neutron port-create --name=port some_network neutron port-delete port Deleted port: port In the neutron-server log we can see: http://paste.openstack.org/show/483517/ Apart from the scary TRACE there's no real implications. What should have happened is an early return, so the l2pop mech driver shouldn't be doing anything in this case, and it's spamming the log with bogus information instead. Similarly, when updating the IP address of an unbound port, a 'chg_ip' RPC message is fanout when there's no need to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1533013/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
