Hi,
yes, I did witness background agents crashing when they tried to upgrade
the puppet packages. The postinst script would try to restart the
service, and kill the agent in the process (leaving the package half
configured. What fun).
This might work better with newer versions, but with the 2.7.x ones, I'd
definitely advise caution.
I worked around this by making Puppet register an at job that would
perform the update, instead of Puppet itself doing so.
HTH,
Felix
On 10/23/2014 11:54 AM, Kai Timmer wrote:
> Hello,
> I'm running a puppetmaster in version 3.7.1 and most of my puppet
> agents are kept in the Debian wheezy version (2.7.23-1~deb7u3). This
> works fine for me, so from my point of view there is no need to
> immediately upgrade my agents, but when I do I would like a way to do
> this with puppet.
>
> Something like this:
> package {['puppet', 'puppet-common'],
> ensure => "$puppetversion",
> notify => 'puppet-agent',
> }
>
> I'm just curios if that would be a good Idea? Wouldn't this break my
> current puppet run?
>
> How do you upgrade your agents? Whats best practise here?
>
> Thanks,
> Kai
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/545AD948.5070303%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.
