SystemExit exception should be logged in neutron
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Xiang Hui |
Bug Description
OS : RHEL6.4
OpenStack version :Havana
Config /etc/neutron/
# L3 requires that an interface driver be set. Choose the one that best
# matches your plugin.
# interface_driver =
# Example of interface_driver option for OVS based plugins (OVS, Ryu, NEC)
# that supports L3 agent
# interface_driver = neutron.
Then start neutron-l3-agent :
service neutron-l3-agent start
The result is :
[root@xianghui ~]# service neutron-l3-agent start
Starting neutron-l3-agent: [ OK ]
[root@xianghui ~]# ps -ef|grep neutron-l3-agent
root 28989 6164 0 04:38 pts/2 00:00:00 grep --color=auto neutron-l3-agent
Actually, neutron-l3-agent isn't been started, but there's no log can be tracked both in user interface or in /var/log/
Changed in neutron: | |
assignee: | nobody → Xiang Hui (xianghui) |
Changed in neutron: | |
status: | Confirmed → In Progress |
Changed in neutron: | |
milestone: | none → havana-rc1 |
importance: | Undecided → Low |
tags: | added: l3-ipam-dhcp |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | havana-rc1 → 2013.2 |
actually, there is a message printed in screen immediately when l3 fails:
An interface driver must be specified
so the bug title is not very suitable, however, i think logging this error makes sense, because sometimes operator may modify config files and reboot at once but may ignore this screen message when system restart, so log is needed
i think you can modify the title to 'systemExit exception should be logged in l3_agent' (and you can make a universal change for all systemExit in neutron not only in l3, this is optianal)
mark as comfirm