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

[Russ Allbery]

Niels Thykier <niels at thykier.net> writes:

> Do a similar thing apply for the 2.7 -> 3.7 upgrade, or are there any
> other things people should be aware of before the upgrade (e.g. are
> puppet 2.7 manifests compatible with 3.7)?
>   If you have the time, I would strongly prefer you proposed the initial
> wording of such a paragraph (if needed) as you most likely know the
> issues better than I will.

Puppet 2.7 manifests are not necessarily compatible with 3.7, since some
deprecated constructs are no longer supported.  The list of changes is
fairly extensive; the short version is that anything that the Puppet
master was logging deprecation warnings about will probably need to be
fixed.  Puppet 3.x also changes the scoping rules, which may cause
significant problems for some manifests.

As with all Puppet upgrades, the Puppet master servers must be upgraded
before any client.

It would be nice to say something more specific, but some quick searching
didn't uncover any simple Puppet upgrade guide.  The best that I found
was:

    http://somethingsinistral.net/blog/the-angry-guide-to-puppet-3/

which at least talks about the scoping change.  But there are some other
changes, such as adding /modules/ to Puppet resource URLs, that need to be
done as well.

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>