swiftinit service provider can't work on xenial

Bug #1578408 reported by Emilien Macchi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-swift
Fix Released
High
Adam Vinsh

Bug Description

See lib/puppet/provider/service/swiftinit.rb
It's hardcoded that for ubuntu we use init, while we should use systemd.

Changed in puppet-swift:
importance: Undecided → High
status: New → Confirmed
Changed in puppet-swift:
assignee: nobody → Adam Vinsh (adam-vinsh)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to puppet-swift (master)

Reviewed: https://review.openstack.org/316270
Committed: https://git.openstack.org/cgit/openstack/puppet-swift/commit/?id=d705401750e648ffce6c40f1a5a494683acdfa69
Submitter: Jenkins
Branch: master

commit d705401750e648ffce6c40f1a5a494683acdfa69
Author: Adam Vinsh <email address hidden>
Date: Fri May 13 20:13:34 2016 +0000

    Support xenial with swift-init service provider

    Added function to check if ubuntu is < 16.04.
    If ubuntu < 16.04 then default provider was upstart.
    If ubuntu = 16.04 then use systemd support.

    Closes-Bug: #1578408

    Change-Id: Icb2d6ff5152e782066b957d5e6e74357496c6b28

Changed in puppet-swift:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/puppet-swift 9.0.0

This issue was fixed in the openstack/puppet-swift 9.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.