Comment 7 for bug 1210121

I was just able to reproduce this on my Havana setup.

From /var/log/neutron/server.log:
=====
.
.

2013-11-22 05:36:03.150 2138 INFO neutron.common.config [-] Logging enabled!
2013-11-22 05:36:03.154 2138 ERROR neutron.common.legacy [-] Skipping unknown group key: firewall_driver
2013-11-22 05:36:03.175 2138 INFO neutron.common.config [-] Config paste file: /etc/neutron/api-paste.ini
2013-11-22 05:36:03.425 2138 INFO neutron.manager [-] Loading Plugin: neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2
2013-11-22 05:36:03.670 2138 INFO neutron.plugins.openvswitch.ovs_neutron_plugin [-] Network VLAN ranges: {}
2013-11-22 05:36:03.760 2138 INFO neutron.plugins.openvswitch.ovs_neutron_plugin [-] Tunnel ID ranges: [(1, 1000)]
.
.
=====

Despite:

$ systemctl status neutron-server
neutron-server.service - OpenStack Quantum Server
   Loaded: loaded (/usr/lib/systemd/system/neutron-server.service; enabled)
   Active: active (running) since Fri 2013-11-22 05:36:02 EST; 3min 24s ago
 Main PID: 2138 (neutron-server)
   CGroup: /system.slice/neutron-server.service
           └─2138 /usr/bin/python /usr/bin/neutron-server --config-file /usr/share/neutron/neutron-dist.conf --config-file /etc/neutron/neutron.con...

This is clearly a benign "ERROR" as noted from the previous comments. (But, unsuspecting users might be confused.)