Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-6963

Puppet doesn't detect systemd as default service provider on CoreOS

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.9.0
    • Component/s: None
    • Labels:
    • Template:
    • Acceptance Criteria:
      Hide

      Puppet should use the systemd service provider to query and interact with services in CoreOS. This can be verified by running puppet resource service --param provider to see which provider is being used to manager services.

      Show
      Puppet should use the systemd service provider to query and interact with services in CoreOS. This can be verified by running puppet resource service --param provider to see which provider is being used to manager services.
    • Team:
      Puppet Developer Experience
    • Story Points:
      1
    • Sprint:
      PDE 2016-12-14
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Previously, the systemd service provider did not specify itself as the default for CoreOS systems. Since systemd is the default service manager in CoreOS, this change updates the provider to add the CoreOS family to its defaults.
    • QA Risk Assessment:
      No Action
    • QA Risk Assessment Reason:
      no coreOS test infrastructure available, covered by unit tests

      Description

      CoreOS is correctly identified by facter (https://github.com/puppetlabs/facter/blob/11288d2a33caec577fe696bd02e4bed12e5ac12d/lib/inc/internal/facts/linux/os_coreos.hpp) but when trying to manage services Puppet detects both init.d and systemd and defaults to init.d. In reality CoreOS uses systemd for all service management.

      Expected behaviour: The service provider should use systemd as the default provider for CoreOS

        Attachments

          Activity

            People

            • Assignee:
              davideagle Davíð Ö Jóhannsson
              Reporter:
              gareth Gareth Rushgrove
              QA Contact:
              Eric Thompson
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support