Service provider "init" is not valid in Puppet 4 on Ubuntu

[Cody Herriges]

puppet-openstack-integration jobs fail on Puppet 4 due to the use of the "init" provider on Ubuntu systems, which is now intentionally disabled to avoid issues with its ability to properly manage services without unit files. Use of the "init" provider should be replaced with "debian" which is available in Puppet 4 and Puppet 3.

https://tickets.puppetlabs.com/browse/PUP-5016
https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/299773
Committed: https://git.openstack.org/cgit/openstack/puppet-ceph/commit/?id=635227c39b8f143c8bfc840325a42bee9e79c647
Submitter: Jenkins
Branch: master

commit 635227c39b8f143c8bfc840325a42bee9e79c647
Author: Cody Herriges <email address hidden>
Date: Wed Mar 30 23:28:05 2016 -0700

    Set OS specific init service providers

      This commit replaces the use of the "init" provider for services with
      OS specific ones, "redhat" and "debian".

      This is to get around that fact that "init" is explicitely disabled on
      Ubuntu for Puppet 4[1] and we've seen other issues where Puppet's systemd
      provider doesn't understand "static" as a service enabled state.
      Falling back to the legacy provider that inherits from "init" should
      provide us the same functionality.

      [1] https://tickets.puppetlabs.com/browse/PUP-5016
      [2] https://tickets.puppetlabs.com/browse/PUP-5353

    Change-Id: Ib16ef8e15cccde1ee19198eaf387daecc031450d
    Closes-Bug: #1564203

[Cody Herriges (ody-cat)]

Marked this bug as invalid for puppet-swift. There was a different init issue affecting swift that was actually related to endpoint unavailability.