L2pop raises exception when deleting an unbound port
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Networking ML2 Generic Switch |
Undecided
|
Unassigned | ||
| neutron |
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 |
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 2540c84c7624892
Author: Assaf Muller <email address hidden>
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:/
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: Ia81c03dcdf7aef
Closes-Bug: #1533013
Changed in neutron: | |
status: | In Progress → Fix Released |
This issue was fixed in the openstack/neutron 8.0.0.0b2 development milestone.
We are getting this issue in Newtton/Stable neutron:9.1.2.
Kevin Benton (kevinbenton) wrote : | #5 |
Can you please provide a traceback?
Here is the code for update_device_up in newton and it has the early return: https:/
Kevin Benton (kevinbenton) wrote : | #6 |
Sorry, I was looking at the wrong branch. This is still susceptible to tracebacks.
Kevin Benton (kevinbenton) wrote : | #7 |
I think what you are hitting is slightly different. It must not be an unbound port if an 'agent_host' value is being passed in that makes it through this conditional.
Related fix proposed to branch: master
Review: https:/
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit c7fb24b3cb9cda1
Author: Kevin Benton <email address hidden>
Date: Mon Mar 13 15:06:22 2017 -0700
Check for None in _get_agent_fdb for agent
get_
driver so we need to check for that case before
we blindly try to decode configuration values on
the result.
There are a couple of cases that can lead to this.
* The deployment can be misconfigured and is missing
either a tunneling_ip option for the agent on a
host or is missing an L2 agent with that host_id
entirely.
* Multiple mech drivers are in use and a port is being
deleted from an agentless host.
Related-Bug: #1533013
Closes-Bug: #1672564
Change-Id: I1e79f600172eda
冯龙飞 (longfei.feng) wrote : | #10 |
2017-03-27 11:31:23.510 58098 ERROR neutron.
2017-03-27 11:31:23.510 58098 ERROR neutron.
2017-03-27 11:31:23.510 58098 ERROR neutron.
2017-03-27 11:31:23.510 58098 ERROR neutron.
2017-03-27 11:31:23.510 58098 ERROR neutron.
2017-03-27 11:31:23.510 58098 ERROR neutron.
2017-03-27 11:31:23.510 58098 ERROR neutron.
2017-03-27 11:31:23.510 58098 ERROR neutron.
2017-03-27 11:31:23.510 58098 ERROR neutron.
2017-03-27 11:31:23.510 58098 ERROR neutron.
2017-03-27 11:31:23.510 58098 ERROR neutron.
2017-03-27 11:31:23.510 58098 ERROR neutron.
2017-03-27 11:31:23.510 58098 ERROR neutron.
2017-03-27 11:31:23.510 58098 ERROR neutron.
2017-03-27 11:31:23.511 58098 DEBUG networking_
Esha Seth (eshaseth) wrote : | #11 |
I am facing the same issue in ocata, I tried this defect fix https:/
Related fix proposed to branch: stable/ocata
Review: https:/
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: stable/ocata
commit f15031f406b61f1
Author: Kevin Benton <email address hidden>
Date: Mon Mar 13 15:06:22 2017 -0700
Check for None in _get_agent_fdb for agent
get_
driver so we need to check for that case before
we blindly try to decode configuration values on
the result.
There are a couple of cases that can lead to this.
* The deployment can be misconfigured and is missing
either a tunneling_ip option for the agent on a
host or is missing an L2 agent with that host_id
entirely.
* Multiple mech drivers are in use and a port is being
deleted from an agentless host.
Related-Bug: #1533013
Closes-Bug: #1672564
Change-Id: I1e79f600172eda
(cherry picked from commit c7fb24b3cb9cda1
tags: | added: in-stable-ocata |
Fix proposed to branch: master /review. openstack. org/266114
Review: https:/