Jira (PUP-3483) Systemd provider doesn't scan for changed units
Title: Message Title Tom Limoncelli commented on PUP-3483 Re: Systemd provider doesn't scan for changed units Thomas Mueller I think we agree on all points except I feel that https://forge.puppet.com/camptocamp/systemd should be make part of puppet so that everyone uses the same one. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3483) Systemd provider doesn't scan for changed units
Title: Message Title Tom Limoncelli commented on PUP-3483 Re: Systemd provider doesn't scan for changed units (If anyone would like to discuss this at PuppetConf 2016, I'd like to hash it out and get consensus.) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-3483) Systemd provider doesn't scan for changed units
Title: Message Title Tom Limoncelli commented on PUP-3483 Re: Systemd provider doesn't scan for changed units R.I.Pienaar I'm glad there is a precedent. So, if there is a puppetlabs-apt, we need a puppetlabs-systemd? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-3483) Systemd provider doesn't scan for changed units
Title: Message Title Tom Limoncelli commented on PUP-3483 Re: Systemd provider doesn't scan for changed units I think the best solution is the ::systemd module from camptocamp: Any time you modify a unit file (.service) have it notify Exec['systemctl-daemon-reload']. https://github.com/camptocamp/puppet-systemd The problem, however, is that modules like puppetlabs-firewall can't be expected to depend on a third-party module like camptocamp/puppet-systemd. The correct solution is for Puppet to make The One True Exec['systemctl-daemon-reload'] and have everyone standardize on it. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-3483) Systemd provider doesn't scan for changed units
Title: Message Title
Tom Limoncelli commented on PUP-3483
Re: Systemd provider doesn't scan for changed units
It is now 3 months later and it looks like the recommended solution has an unintentional negative side-effect.
Many modules need this kind of functionality. They all do what you've recommended: Create a `Exec['systemd-tmpfiles-create']` which can be notify'ed any time a unit file is installed or modified. However, now many different modules use the same name and collide. If they use different names, systemd is told to "daemon-reload" multiple times, instead of having all the notify's collapsed into one Exec{}.
There are probably many solutions but one would be: Puppet Labs should bless a single module that defines the Exec[], so that all other modules can notify it. A module such as https://github.com/camptocamp/puppet-systemd would be a candidate, though I think the name should be different.
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2103) Puppet client does not update and does consult the crl during authentication
Title: Message Title Tom Limoncelli created an issue Puppet / PUP-2103 Puppet client does not update and does consult the crl during authentication Issue Type: Bug Affects Versions: 3.4.3 Assignee: Unassigned Created: 31/Mar/14 11:04 AM Priority: Critical Reporter: Tom Limoncelli I my tests puppet client never updates it’s /var/lib/puppet/ssl/crl.pem from the master when it changes. Though the CRL is initially downloaded from a CA and ‘cached’ that cache is never cleared causing multi-master setups to run with an increasingly outdated CRL. I think this bug is dangerous especially because the separate CA thing is new and people don’t realize, nor is it documented, that this is the current behavior. Add Comment
