Jira (PUP-9473) Systemd daemon-reload doesn't get triggered for removal of unit file
Title: Message Title Tim Meusel commented on PUP-9473 Re: Systemd daemon-reload doesn't get triggered for removal of unit file Hey puppet. This is currently marked as 'needs information'. Is that state correct? Is there anything missing from Ewouds description? andreas.pa...@univie.ac.at I don't think your suggestion is the correct way forward. This is a valid workaround, but not a valid bugfix. Puppet has a built-in szstemctl daemon-reload since 6.1, it's just not triggered correctly in all usecase. See https://tickets.puppetlabs.com/browse/PUP-3483 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.294694.154930163.15898.1644912600063%40Atlassian.JIRA.
Jira (PUP-9473) Systemd daemon-reload doesn't get triggered for removal of unit file
Title: Message Title
Andreas Papst commented on PUP-9473
Re: Systemd daemon-reload doesn't get triggered for removal of unit file
Hello, To find changed unit-files use:
$ systemctl --all status *.service 2>&1 | grep --color 'changed on disk. Run' Warning: The unit file, source configuration file or drop-ins of example.service changed on disk. Run 'systemctl daemon-reload' to reload units.
For a distinct service, it would be
$ systemctl --all status example.service 2>&1 | grep --color 'changed on disk. Run' && echo changed
BTW: `systemctl daemon-reload´ mends all deltas. Therefore I suggest, you use a trigger to a global Exec['/bin/systemctl daemon-reload'] for all changes and a `ensure => Exec['/bin/systemctl daemon-reload']´ within the Service statement. The statement {{exec['/bin/systemctl daemon-reload'] {refreshonly => true,} }} should be part of modules/systemd/manifest/init.pp. Example:
file { '/usr/lib/systemd/system/foo.service': ensure => file, owner => 'root', group => 'root', mode => '0644', source => "puppet:///modules/${module_name}/foo.service", notify => Exec['/bin/systemctl daemon-reload'], } ~> service
Unknown macro: {'foo'}
Just have a look at https://github.com/justin8/justin8-systemd Regards Andreas
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PUP-9473) Systemd daemon-reload doesn't get triggered for removal of unit file
Title: Message Title Ewoud Kohl van Wijngaarden commented on PUP-9473 Re: Systemd daemon-reload doesn't get triggered for removal of unit file This showed up in https://github.com/puppetlabs/puppetlabs-postgresql/pull/1233 as well. From that PR, the root cause is that querying for the property failed: # systemctl show --property=NeedDaemonReload -- postgresql Failed to get properties: Access denied Perhaps the safest bet is to treat an access denied as needs reload. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (PUP-9473) Systemd daemon-reload doesn't get triggered for removal of unit file
Title: Message Title Geoff Nichols assigned an issue to Branan Riley Puppet / PUP-9473 Systemd daemon-reload doesn't get triggered for removal of unit file Change By: Geoff Nichols Assignee: Branan Riley Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9473) Systemd daemon-reload doesn't get triggered for removal of unit file
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9473 Systemd daemon-reload doesn't get triggered for removal of unit file Change By: Josh Cooper Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9473) Systemd daemon-reload doesn't get triggered for removal of unit file
Title: Message Title Duncan X Simpson created an issue Puppet / PUP-9473 Systemd daemon-reload doesn't get triggered for removal of unit file Issue Type: Bug Affects Versions: PUP 6.1.0 Assignee: Unassigned Components: Types and Providers Created: 2019/02/04 9:33 AM Priority: Minor Reporter: Duncan X Simpson 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 Add Comment
