Jira (PUP-11401) Non-profiled CodeHeap size is constantly growing
Title: Message Title Justin Stoller assigned an issue to Pavel Sapezhka Puppet / PUP-11401 Non-profiled CodeHeap size is constantly growing Change By: Justin Stoller Assignee: Justin Stoller Pavel Sapezhka 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.428106.1640164262000.6707.1642794480037%40Atlassian.JIRA.
Jira (FACT-3001) Debug output shows facter gets called thousands of times
Title: Message Title Michiel van de Garde commented on FACT-3001 Re: Debug output shows facter gets called thousands of times Seeing this issue in PE 2021.4 (agent 7.12.1/server 7.4.2/facter 4.2.5). Also seems to be confined to agent runs on windows. Logs show pretty much the same as those provided by kuc . 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.393130.1617033494000.5772.1642777920036%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-11326) Make regsubst() sensitive-aware
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-11326 Make regsubst() sensitive-aware Change By: Ciprian Badescu Sprint: NW - 2022-01-27 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.420572.1634905979000.5650.1642759200100%40Atlassian.JIRA.
