Bug 1098121
| Summary: | neutron-vpn-agent does not use the /etc/neutron/fwaas_driver.ini | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Attila Fazekas <afazekas> | |
| Component: | openstack-neutron | Assignee: | Ihar Hrachyshka <ihrachys> | |
| Status: | CLOSED ERRATA | QA Contact: | Ofer Blaut <oblaut> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 5.0 (RHEL 7) | CC: | chrisw, ihrachys, lpeer, mlopes, nyechiel, sclewis, yeylon | |
| Target Milestone: | rc | |||
| Target Release: | 5.0 (RHEL 7) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-neutron-2014.1-20.el7ost | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, 'neutron-vpn-agent' did not apply configuration options from the fwaas_driver.ini file, due to a missing argument in the service files. In addition, the legacy L3 agent did refer to the 'fwaas_driver.ini' file. This resulted in inconsistent L3 agent configuration procedures.
With this update, service files have been updated to ensure the configuration file is read on agent startup.
As a result, configuration in the fwaas_driver.ini file is now applied to neutron-vpn-agent.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1098578 1098596 1098601 (view as bug list) | Environment: | ||
| Last Closed: | 2014-07-08 15:36:33 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1098578, 1098596, 1098601 | |||
|
Description
Attila Fazekas
2014-05-15 10:53:47 UTC
To clarify things up... 1. The bug is present in both RHOS 4 and RHOSP 5 (both branches). 2. Devstack applies the conf file to vpn agent [1], so we should probably also do it. 3. VPN agent replaces L3 agent, and L3 agent uses the conf file, so this is another reason why we need to read the conf file for the agent. [1]: https://github.com/openstack-dev/devstack/blob/master/lib/neutron#L498 And the bug is present in RDO too. FYI the fix for Icehouse branches is built (see Fixed in Version field). For RHOS 4, there is no flags needed to push the change and build the new package (requested acks from PMs). As for RDO, builds are still in progress: http://copr.fedoraproject.org/coprs/jruzicka/rdo-havana-epel-6/builds/ http://copr.fedoraproject.org/coprs/jruzicka/rdo-icehouse-epel-6/builds/ http://copr.fedoraproject.org/coprs/jruzicka/rdo-icehouse-epel-7/builds/ Once complete, I'll send rdo-update.
Tested ( RHEL 7 )
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
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-0848.html |