Bug 1302275 - neutron-l3-agent does not start on Mitaka-2 when enabling FWaaS
Summary: neutron-l3-agent does not start on Mitaka-2 when enabling FWaaS
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: trunk
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: trunk
Assignee: Javier Peña
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-27 10:57 UTC by Javier Peña
Modified: 2017-06-18 06:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-18 06:12:19 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 272995 0 None None None 2016-01-27 11:07:54 UTC

Description Javier Peña 2016-01-27 10:57:07 UTC 
Description of problem: 
On a packstack-deployed environment using the RDO bits from the Mitaka-2 test day, with CONFIG_NEUTRON_FWAAS=y, neutron-l3-agent fails. /var/log/neutron/l3-agent.log shows the following:


2016-01-27 11:43:28.097 31375 CRITICAL neutron [req-5cbe0ca7-1e73-48b8-8c66-54ec0d6fdf88 - - - - -] ValueError: Configuration error - no FWaaS device_driver specified


Version-Release number of selected component (if applicable):
openstack-packstack-puppet-8.0.0-dev1741.g72faffe.el7.centos.noarch
openstack-packstack-8.0.0-dev1741.g72faffe.el7.centos.noarch

How reproducible: always


Additional info:

Running the following command added the missing option to /etc/neutron/fwaas_agent.ini and allowed the L3 agent to start without errors:

openstack-config --set /etc/neutron/fwaas_driver.ini fwaas driver neutron_fwaas.services.firewall.drivers.linux.iptables_fwaas.IptablesFwaasDriver
Comment 1 Javier Peña 2016-01-27 11:07:55 UTC 
Proposed https://review.openstack.org/272995 with a fix.
Comment 2 Mike McCune 2016-03-28 22:48:26 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 4 Christopher Brown 2017-06-17 19:04:21 UTC 
Javier,

This one too, looks like it can be closed now.
Note You need to log in before you can comment on or make changes to this bug.