ODL L3 configuration still uses the neutron-l3-agent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-odl |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Used devstack(
In the local.conf, added ODL_L3=True, which according to the below link should not use the neutron-l3-agent.
https:/
But, when stacking noticed that the l3-agent is actually configured and used
Parts from stack.sh log
--8<------
iniset /etc/neutron/
|
|
2016-04-20 20:20:50.885 | + run_process q-l3 '/usr/bin/
2016-04-20 20:20:50.885 | + local service=q-l3
2016-04-20 20:20:50.885 | + local 'command=
2016-04-20 20:20:50.885 | + local group=
2016-04-20 20:20:50.885 | + is_service_enabled q-l3
2016-04-20 20:20:50.888 | + return 1
-------8<---------
local.comf can be checked in the console log:https:/
the stacking log: https:/
The same behavior is observed even if we test this with devstack(
I looked at the log.
> 2016-04-20 20:20:50.885 | + is_service_enabled q-l3
> 2016-04-20 20:20:50.888 | + return 1
In bash, 1 means false. (Ah, very un-intuitive for C programmer...), so run_process skips to run neutron-l3-agent.
Can you please double-check if screen consnole have q-l3 or not?
For now I mark this bug report invalid.
Once you really find neutron-l3-agent is running in screen console, please feel free to mark it valid again.