L2pop raises exception when deleting an unbound port
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Networking ML2 Generic Switch |
Invalid
|
Undecided
|
Unassigned | ||
neutron |
Fix Released
|
Low
|
Assaf Muller |
Bug Description
Some brilliant individual introduced a regression during a refactor (https:/
neutron port-create --name=port some_network
neutron port-delete port
Deleted port: port
In the neutron-server log we can see:
http://
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.
description: | updated |
Fix proposed to branch: master /review. openstack. org/266114
Review: https:/