When installing OSP-7 with packstack and enabling "VPNaaS" in answer file it install VPNaaS with openswan driver when it should be liberswan. Driver configuration should be : In vpnagent.ini: [vpnagent] vpn_device_driver=neutron_vpnaas.services.vpn.device_drivers.libreswan_ipsec.LibreSwanDriver In /etc/neutron/neutron.conf service_plugins = neutron.services.vpn.plugin.VPNDriverPlugin In /etc/neutron/neutron_vpnaas.conf service_provider=VPN:libreswan:neutron_vpnaas.services.vpn.service_drivers.ipsec.IPsecVPNDriver:default How reproducible: always Steps to Reproduce: 1.deploy with packstack osp-8 and enable vpnass 2.verify in vpnagent.ini which driver is used 3. Actual results: Expected results: Additional info:
opened on version : [root@osp-7-packstack ~]# rpm -qa |grep vpn openstack-neutron-vpnaas-2015.1.2-1.el7ost.noarch python-neutron-vpnaas-2015.1.2-1.el7ost.noarch [root@osp-7-packstack ~]# rpm -qa |grep packstack openstack-packstack-2015.1-0.15.dev1589.g1d6372f.el7ost.noarch openstack-packstack-puppet-2015.1-0.15.dev1589.g1d6372f.el7ost.noarch
@Brent - Just making sure that Packstack should indeed configure libreswan by default.
@Assaf - yes, this is correct. AFAIK, RHEL 7 doesn't come with any other "Swan", so LibreSwan is "it".
this fix has been merged in master, backporting to liberty. can i have acks for this bug?
(In reply to Ivan Chavero from comment #5) > this fix has been merged in master, backporting to liberty. > > can i have acks for this bug? As you noticed simply moving the bug to ASSIGNED grants all three ACKs, there's no need to needinfo on rhos-flags anymore :)
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. https://access.redhat.com/errata/RHBA-2016:1354