[Pkg-puppet-devel] [release-notes] Any known issues with Puppet 2.7 -> 3.7 upgrade?

[micah]

Stig Sandbeck Mathisen <ssm at debian.org> writes:

> That has improved, somewhat, I can run a puppet 2.7 master for clients
> up to at least version 3.4, with very few problems other than extra
> warnings and complaints at runtme.
>
> Puppet agents version 3.6 and 3.7, on the other hand, has problems when
> I run it against a puppet master version 2.7 at work. They have to run
> against a puppet 3.x master.

Hmm, this means that we are potentially making a difficult situation for
people. If a 2.7 master doesn't work with 3.7 and Jessie has puppet
3.7.2, and a master must be upgraded before the clients, then that means
that the puppetmaster needs to be upgraded before any clients, and you
cannot do that upgrade until you "fix" all your puppet code.

In the past it was possible for people to upgrade clients before their
master, which was useful for doing a doing a rolling upgrade and slow
migration of manifests.

I think we should make it really clear that if you upgrade any client
machine to jessie before you upgrade your master, that machine will not
be able to do puppet runs (unless you pin a wheezy version of puppet and
not upgrade it, which does actually work).

micah