puppet agent upgrade with puppet module

[Kai Timmer]

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

[Pete Brown]

Hi Kai,

That is basically how I do it and I haven't see any issues so far.
I haven't upgraded quite as far as you intend and I would give it a
test in vagrant to see how it goes first.

Incidentally I do the same with facter, hiera and the server packages
as well and don't see any issues with upgrading those either.

Good luck with it.

Pete.

> --
> 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...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/c22bc207-47e6-4997-afec-193e33664d5a%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
Pete Brown
Director and Primary Systems Engineer
Abstract IT Pty Ltd.

[Felix Frank]

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

[Pete Brown]

On 6 November 2014 12:13, Felix Frank <Felix...@alumni.tu-berlin.de> wrote:
> 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 haven't had any noticeable issues with 3.6 and above on Ubuntu.

I do have a client that is still running 2.7 on CentOS 5 so thanks for
the heads up. :)

> I worked around this by making Puppet register an at job that would
> perform the update, instead of Puppet itself doing so.

Awesome idea.
I may yoink that for my module.

> 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...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/545AD948.5070303%40Alumni.TU-Berlin.de.

[Felix Frank]

On 11/07/2014 01:26 PM, Pete Brown wrote:
> I do have a client that is still running 2.7 on CentOS 5 so thanks for
> the heads up. :)

The RPMs might generally handle this more gracefully than the debs. I
cannot comment on that.