You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Drop Puppet 4 and 5 support + daemon-reload code (voxpupuli#171)
* Drop Puppet 4 and 5 support
This picks version 6.1.0 as a new lower bound since that contains code
to automatically run daemon-reload if needed. Versions 4 and 5 are EOL.
* Drop daemon-reload code
Since Puppet 6.1.0 it's no longer needed to run daemon-reload manually
when restarting a service. That means it's possible to drop this code.
* Implement a workaround for PUP-9473.
Prior to this commit, the follow code did not suffer from PUP-9473:
systemd::unit_file { 'myservice.service':
ensure => absent,
active => true,
}
That's because the module considers that an invalid state and fails to
compile.
The follow code did trigger the bug:
systemd::unit_file { 'myservice.service':
ensure => absent,
}
service { 'myservice':
ensure => running,
require => Systemd::Unit_file['myservice.service'],
}
That's precisely what happens when a module switches from a
module-provided unit file to a package-provided unit file.
Systemd caches unit files and their relations. This means it needs to reload, typically done via `systemctl daemon-reload`. Since Puppet 6.1.0 ([PUP-3483](https://tickets.puppetlabs.com/browse/PUP-3483)) takes care of this by calling `systemctl show $SERVICE -- --property=NeedDaemonReload` to determine if a reload is needed. Typically this works well and removes the need for `systemd::systemctl::daemon_reload` as provided prior to camptocamp/systemd 3.0.0. This avoids common circular dependencies.
227
+
228
+
It does contain a workaround for [PUP-9473](https://tickets.puppetlabs.com/browse/PUP-9473) but there's no guarantee that this works in every case.
229
+
243
230
### network
244
231
245
232
systemd-networkd is able to manage your network configuration. We provide a
0 commit comments