VPNaaS packages name change for Ubuntu

Bug #1825700 reported by Matthew J Black
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-neutron
Fix Released
Undecided
Matthew J Black

Bug Description

This is related to #1474797 but the fix for that bug did not update the package for Ubuntu. The other issue relating to the package names is that for Ubuntu there is no openswan package and needs to be changed to strongswan.

Changed in puppet-neutron:
assignee: nobody → Matthew J Black (mjblack)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to puppet-neutron (master)

Reviewed: https://review.opendev.org/654011
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=46b1e4d02e4132880ac5b28600c41775418ca488
Submitter: Zuul
Branch: master

commit 46b1e4d02e4132880ac5b28600c41775418ca488
Author: Matthew J. Black <email address hidden>
Date: Sat Apr 20 09:56:25 2019 -0400

    Fix incorrect VPNaaS packages

    As of Queens the VPNaaS package to be used is no longer
    neutron-vpn-agent and has been replaced with the package
    python-neutron-vpnaas.

    The package for openswan does not exist for Debian systems
    and needs to be updated to strongswan instead.

    Change-Id: I859c80facc9dadf461c2300a6c354c73ae60e5e4
    Closes-bug: #1825700

Changed in puppet-neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/puppet-neutron 15.0.0

This issue was fixed in the openstack/puppet-neutron 15.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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