Issue #7273 has been updated by Noah Cantor.
I can think of several potential reasons to change puppet.conf and not want puppet to wait until the next run to pick up the information: A new report server; an updated run interval (current load is too high, or there's some testing that needs to be done by the puppet agent); you want to move your puppetmaster from one URL to another (or IP). I use puppet to manage my entire infrastructure. All systems, all services, all configurations, all packages, all files... everything that's non-standard. So why is it that when I want to use puppet to manage itself (as seems incredibly intuitive), that it's incapable of doing it? I upgrade puppet via puppet. Sometimes that involves changes in puppet.conf. When I'm ready to roll out to the newest release, I tell my puppet installation that the new version is 2.7.1 (for example). When that gets rolled out, puppet dies. That's completely counter-intuitive. When I want to run tests on a handful of servers, I create the tests, run things manually, then add things to puppet and run puppet manually (via puppetd), then run things via puppet and the config file (/etc/init.d/puppet). In numerous cases, I have wanted to make rapid changes to systems. In order to properly test this via puppet, I want to change the frequency of system checks. Normally, they're scheduled at 1/hr. When testing, I change them to 12/hr, in puppet.conf. Changing that on 15-20 servers, manually, would be a serious pain. I think the main point is that Puppet can manage everything on a system -- all files, packages, services, -- except itself. Where is the logic in that? Should I install Chef to ensure that puppet gets restarted when the config changes? ---------------------------------------- Bug #7273: Modifying puppet.conf causes 'reparsing config' and TERM signal results in shutdown of daemon https://projects.puppetlabs.com/issues/7273 Author: Randall Hansen Status: Investigating Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: ... waiting for details from Ryan Conway ... -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
