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

systemd service provider only works on running systems

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: PUP 6.14.0
    • Fix Version/s: None
    • Component/s: Types and Providers
    • Labels:
      None
    • Template:
      PUP Bug Template
    • Team:
      Night's Watch
    • Sprint:
      ready for triage
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Puppet Version: 6.14.0
      Puppet Server Version:
      OS Name/Version: Any systemd-based linux

      The systemd service provider "is not functional on this host" in a systemd-nspawn container running without `-boot` or with `-as-pid2`. In these cases there is a separate PID namespace and PID 1 is not systemd. This is because the current "confines" in `providers/service/systemd.rb` checks for "systemd" in `/proc/1/comm`.

      Desired Behavior:

      Using systemctl to enable/disable/mask units only needs `/usr/bin/systemctl` to exist. If possible I could see having different behavior for handling `ensure` vs `enable` based on PID1. However, when setting up a container image, I should be able to enable/disable/mask services.

       

       

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            matt@monaco.cx Matthew Monaco
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:

                Zendesk Support