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

3.x systemd enables in the wrong order breaking puppet service resources first run.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Won't Fix
    • Affects Version/s: PUP 3.8.0, PUP 3.8.1, PUP 3.8.2, PUP 3.8.3, PUP 3.8.4, PUP 3.8.5, PUP 3.8.6
    • Fix Version/s: None
    • Component/s: Catalog Application
    • Labels:
      None
    • Environment:
    • Template:

      Description

      This issue has been fixed in 4.x: https://tickets.puppetlabs.com/browse/PUP-4605

      An outstanding unassigned bug from 05/2015 also reports it. https://tickets.puppetlabs.com/browse/PUP-4651 assuming behavior between reported version in that bug and current is the same.

      Service resource systemd provider fails to run systemctl enable first

      The effect is no .service file is generated from the SysV init script using /lib/systemd/system-generators/systemd-sysv-generator.

      Running two services using the same class /define and same parameterized init script usually results in one service running the enable first and working and the other not, Running systemctl enable creates service file correctly for second and next puppet run works implying no issue with the init script itself.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              russmac_aus Russell Maclean
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support