An argument that would make the agent read the /etc/neutron/fwaas_driver.ini configuration file was missing in the previous release's neutron-vpn-agent service files. As a result, neutron-vpn-agent didn't apply configuration from the configuration file. At the same time, the L3 agent that is replaced by neutron-vpn-agent did read the file. This introduced inconsistency in how different L3 agents were configured.
The service files have been updated so that the configuration file is now read on agent startup, and configuration from the file is applied for neutron-vpn-agent.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHEA-2014-0953.html
Tested neutron 9508 1.8 0.1 284176 40664 ? Ss 12:36 0:00 /usr/bin/python /usr/bin/neutron-vpn-agent --config-file /usr/share/neutron/neutron-dist.conf --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/vpn_agent.ini --config-file /etc/neutron/l3_agent.ini --config-file /etc/neutron/fwaas_driver.ini --log-file /var/log/neutron/vpn-agent.log root 9576 0.0 0.0 112640 972 pts/0 S+ 12:36 0:00 grep --color=auto vpn openstack-neutron-vpn-agent-2014.1-22.el7ost.noarch