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.
--
You received this message because you are subscribed to the Googl
On 6 November 2014 12:13, Felix Frank 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).
>
> Th
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
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 upgr
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.
S
