Issue #17160 has been updated by eric sorenson.
Status changed from Unreviewed to Needs More Information
Assignee set to Konrad Scherer
Hi Konrad, thank you for your report. I'm sorry it took a long time to get back
to you. I have looked at this ticket a few times but was not sure how to
respond. Let me make sure I understand--
To your first point, I agree it is not good to have both puppet agent AND
puppetcommander running. But wouldn't it be simple to just override the
package's default (which I think we have to leave because it is the most common
use case) and manage `service {'puppet': enable=>false, ensure=>stopped }` in
your site? That way each run after an upgrade would make sure your site policy
was enforced.
To the second point, I agree that Puppet's handling of shutting itself down
could be more graceful. I have seen this on other software, for example an
application server which will complete current transactions but return an error
to new clients. I think that is a duplicate request of an old bug: #4568.
Please add yourself to that bug and update it with details of your use-case?
I've put this ticket's status into "Needs more Information" and assigned it to
you. Please either (a) update it with the information I've requested and
re-assign it to me if you need more help, or (b) change the status to "Closed"
if you are able to resolve the issue on your own.
----------------------------------------
Feature #17160: Using puppet agent with external agent run schedulers like
puppetcommander
https://projects.puppetlabs.com/issues/17160#change-79904
Author: Konrad Scherer
Status: Needs More Information
Priority: Normal
Assignee: Konrad Scherer
Category:
Target version:
Affected Puppet version:
Keywords:
Branch:
I have been using puppetcommander with puppet for over a year now. I feel this
is the best solution to controlling the load on my puppet masters.
With the puppet package from puppetlabs, after a new puppet agent package is
installed, the puppet agent is automatically started in daemon mode. When using
puppetcommander the mcollective agent puppetd will detect that the agent is
running and send a USR1 signal instead of attempting to run the agent. But now
both the puppet agent and puppetcommander are triggering puppet runs on the
master, which totally negates the load leveling effect.
I would like to have the puppet agent daemon and external agent run schedulers
work better together:
- Make the puppet agent daemon reset the run interval after an agent run
triggered by signal USR1. I have an untested patch to puppet daemon which I
think will handle this here:
https://github.com/kscherer/puppet/tree/reset_next_agent_run_after_signal This
way with a larger runinterval I can get the best of both worlds if
puppetcommander stops running. What do you think?
- Also useful would be a way to tell a currently running puppet agent daemon to
exit after the next run. Currently there is no way that I can tell the puppet
agent service to stop while running puppet. This will kill the puppet agent run
mid run and the run fails. Yes I am using puppet to manage puppet, as it should
be ;-)
Thank you for your time and puppet.
--
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.
