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

Systemd daemon-reload doesn't get triggered for removal of unit file

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Needs Information
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: PUP 6.1.0
    • Fix Version/s: None
    • Component/s: Types and Providers
    • Labels:
    • Template:
      PUP Bug Template
    • Team:
      Night's Watch
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Puppet Version: 6.1.0
      Puppet Server Version: 6.1.0
      OS Name/Version: CentOS 7

      Related to PUP-3483, if I tell puppet to ensure a unit file (i.e. /etc/systemd/system/foobar.service) is absent, and that unit file overrides another unit file (i.e. /usr/share/systemd/system/foobar.service), Puppet removes the override file but doesn't trigger a daemon reload, causing systemd to still use the old, removed unit file's config.

      Desired Behavior: Removing a file in any of the paths listed here should trigger a daemon-reload, just like modifying them

      Actual Behavior: No daemon-reload is triggered

       

        Attachments

          Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. PUP-3483 Systemd provider doesn't scan for changed units

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              virtualdxs Duncan X Simpson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:

                  Zendesk Support