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

Systemd provider doesn't scan for changed units

    XMLWordPrintable

Details

    • Coremunity
    • Platform Core KANBAN
    • Reviewed
    • New Feature
    • When starting or restarting a service, the `systemd` provider checks to see whether the service requires a daemon reload, and reloads the systemd daemon if necessary.

    Description

      When a package updates it's sysvinit script or systemd unit (or for that matter if I were to be manually managing a systemd unit with a file resource), nothing ever tells systemd to check for changed units.

      Typically you would invoke `systemctl daemon-reload` to scan for new and changed units.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. PUP-9473 Systemd daemon-reload doesn't get triggered for removal of unit file

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Needs Information

          Bug - A problem which impairs or prevents the functions of the product. PUP-10149 Systemd provider daemon-reload broken in puppet 6.11.0

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. PUP-9021 [Resource Type: service][Enhancement] Allow a Systemd service to be reload from a notify instead of restart

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed
          links to

          Web Link Pull Request: (PUP-3483) Fix systemd provider to scan for changed units

          Activity

            People

              melissa Melissa Stone
              nljackson Nicholas Jackson
              Eric Thompson Eric Thompson
              Votes:
              25 Vote for this issue
              Watchers:
              43 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support