neutron

unknown group ERROR in q-vpn log after successful tempest run

Bug #1243486 reported by David Kranz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Triaged
Medium
Mark McClain

Bug Description

Happens a lot. For example: http://logs.openstack.org/50/51750/8/check/check-tempest-devstack-vm-neutron/7b73c73/logs/screen-q-vpn.txt.gz

+ ln -sf /opt/stack/new/screen-logs/screen-q-vpn.2013-10-22-201432.log /opt/stack/new/screen-logs/screen-q-vpn.log
+ export PYTHONUNBUFFERED=1
+ PYTHONUNBUFFERED=1
+ exec /bin/bash -c 'cd /opt/stack/new/neutron && /usr/local/bin/neutron-vpn-agent --config-file /etc/neutron/neutron.conf --config-file=/etc/neutron/l3_agent.ini'
2013-10-22 20:20:32.167 3256 INFO neutron.common.config [-] Logging enabled!
2013-10-22 20:20:32.168 3256 ERROR neutron.common.legacy [-] Skipping unknown group key: firewall_driver

Revision history for this message
Mark McClain (markmcclain) wrote :

This is a bug in the compatibility layer for the rename.

Changed in neutron:
importance: Undecided → Medium
status: New → Triaged
assignee: nobody → Mark McClain (markmcclain)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.