Closed jcpunk closed 2 years ago
I wonder if we could we just remove the "enable => true" part of the "systemd-logind" service? I noticed that this isn't really doing anything anyway since the state of this service is "static" in systemd. If the ensure_resource service declaration matches that from puppet-systemd there should be no conflict using the modules together. This also avoids managing the service more than once. Could you verify this works (or not)?
On my site, the podman
module gets parsed before the systemd
module. So the resources are already created via ensure_resource
inside podman
before the systemd
module tries to create them and conflicts.
Any chance for a 0.6.1 release with this patch?
Posted it.
When using https://forge.puppet.com/modules/puppet/systemd the catalog becomes parse order dependant. This change should resolve this issue. It does end up checking the service more than once, but is very non-invasive.