Havana staging:ERROR neutron.common.legacy [-] Skipping unknown group key: firewall_driver

[Ashok kumaran B]

Hi,

I am currently testing Havana-2 staging debians, in neutron server logs I am observing an error like below

"ERROR neutron.common.legacy [-] Skipping unknown group key: firewall_driver"
the same error was observed in dhcp and l3 logs as well. I have also set the firewall driver in plugin.ini but that didnt seem to solve the problem. DHCP agent is inacive and unable to provide IP's to my instances because of this issue I believe.

My configurations
http://paste.openstack.org/show/43561/

Neutron server log
http://paste.openstack.org/show/43562/

[yong sheng gong (gongysh)]

I don't think the inactive dhcp agent is caused by 'Skipping unknown group key: firewall_driver',
but Skipping unknown group key: firewall_driver itself is a bug.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/40871

[Thiago Martins (martinx)]

Still present with "neutron-dhcp-agent 1:2013.2~rc1-0ubuntu2~cloud0"...

==> /var/log/neutron/dhcp-agent.log <==
2013-10-11 03:28:42.829 8485 ERROR neutron.common.legacy [-] Skipping unknown group key: firewall_driver

[Thiago Martins (martinx)]

This BUG is still here with "neutron-dhcp-agent 1:2013.2~rc2-0ubuntu1~cloud0"...

==> /var/log/neutron/dhcp-agent.log <==
2013-10-16 01:16:46.462 9398 ERROR neutron.common.legacy [-] Skipping unknown group key: firewall_driver

[Akihiro Motoki (amotoki)]

This is a bug of the logic to handling the migration from quantum to neutron.
If you set up neutron from scratch, please ignore this message.

The message is really confusing. I hope the abandoned review will be restored.
Otherwise, it is better to improve the wording.

[Attila Fazekas (afazekas)]

Neutron always logging the 'ERROR neutron.common.legacy [-] Skipping unknown group key: firewall_driver' in every gate job on ERROR level.

It is listed for override here:
https://github.com/openstack/neutron/blob/aa3e64f9125e4c41de90213b75b2826bfd663527/neutron/common/legacy.py#L80

If there is no issue to fix, please avoid logging it as an ERROR.

Additional Note:
Here we are configuring a funny driver:
https://github.com/openstack-dev/devstack/blob/14ea1a2b79aa7a9e7fff284b7d534c0038bbaa89/lib/neutron_plugins/ml2#L97

[Kashyap Chamarthy (kashyapc)]

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.)

[Kevin Breit (kbreit)]

I'm able to reproduce it as well using Red Hat packages. It is accompanied by a probably unrelated crash of neutron-server.

[Jacob_DENG (jacob-deng)]

rhel6.5 ERROR neutron.common.legacy [-] Skipping unknown group key: firewall_driver

[Julien (julienitsme)]

I also have the error with a brand new Havana install.

ERROR neutron.common.legacy [-] Skipping unknown group key: firewall_driver

Should we ignore the error ?

[Marco CONSONNI (marco-consonni)]

I noticed the same error in neutron-server's log file.
I presume that the error is issued by any daemon that happens to use a conf file containing the following configuration lines:

[SECURITYGROUP]
firewall_driver = ...

[Armando Migliaccio (armando-migliaccio)]

I'll try to have a stab at it.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/80379

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/80379
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b5ee49623982530bfb3c3fe2eefb9d8ddb6353bc
Submitter: Jenkins
Branch: master

commit b5ee49623982530bfb3c3fe2eefb9d8ddb6353bc
Author: armando-migliaccio <email address hidden>
Date: Thu Mar 13 12:40:01 2014 -0700

    Kill 'Skipping unknown group key: firewall_driver' log trace

    This is done by trying to import the option first. If this
    does not work, emit a warning instead as in most cases this is
    harmless for a number of reasons: a) the service might not
    even need the opt; b) if things do break down the line, we'll
    see bigger traces; c) it's not gonna be long for this legacy
    quantum/neutron stuff to be removed altogether.

    Closes-bug: 1210121

    Change-Id: I34917da9cb6117ee1d42140621c742f503279b6b

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/havana
Review: https://review.openstack.org/96866

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/96866
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=dbbc8338770d2c340903e006dcb3c90c4aad7b29
Submitter: Jenkins
Branch: stable/havana

commit dbbc8338770d2c340903e006dcb3c90c4aad7b29
Author: armando-migliaccio <email address hidden>
Date: Thu Mar 13 12:40:01 2014 -0700

    Kill 'Skipping unknown group key: firewall_driver' log trace

    This is done by trying to import the option first. If this
    does not work, emit a warning instead as in most cases this is
    harmless for a number of reasons: a) the service might not
    even need the opt; b) if things do break down the line, we'll
    see bigger traces; c) it's not gonna be long for this legacy
    quantum/neutron stuff to be removed altogether.

    Closes-bug: 1210121

    Change-Id: I34917da9cb6117ee1d42140621c742f503279b6b
    (cherry picked from commit b5ee49623982530bfb3c3fe2eefb9d8ddb6353bc)