TRACE: attribute error when trying to fetch the router.snat_namespace.name
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
TRACE seen in the vpn-agent log when configured with DVR router.
A recent refactoring to the agent have introduced this problem.
2015-03-11 14:09:03.570 ERROR neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
2015-03-11 14:09:03.570 3909 TRACE neutron.
tags: |
added: vpnaas removed: neutron-vpnaas |
Changed in neutron: | |
milestone: | none → kilo-rc1 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | kilo-rc1 → 2015.1.0 |
Can you point to what test case and suite being run, when this was seen? Wondering what the test setup is. In this case, VPN is trying to create a process manager, when the router is created (although it will later remove it, as there is no VPN service associated with it). As part of that, it tries to get the namespace of the router (via snat_namesapce. name, for DVR) and that is failing.
The question is, why is there not a namespace available for the DVR at this point in time?
In VPN code, this used to obtain the namespace by calling the L3 agent, getting the router, and then looking up the namespace. Changes on the VPN side, are that, instead of calling back to the L3 agent, to get the router, it uses the router passed into the after_router_added method.
Review 162840 may avert the issue (by not looking up the namespace), but it would like to know why this is failing, though.