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

[Stig Sandbeck Mathisen]

Russ Allbery <rra at debian.org> writes:

> 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.

I agree strongly with "Whatever the puppet master logs about deprecation
warnings must be fixed". Taking care of that before upgrading fixes a
lot of potential issues.

https://docs.puppetlabs.com/puppet/3/reference/release_notes.html#puppet-300
is the best list I can find for what to do when upgrading puppet from
2.x to 3.x.

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

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.

(Puppet Labs are preparing puppet version 4, which will break all
backwards compatibility, but that's really outside the scope of the
release notes this time)

-- 
Stig Sandbeck Mathisen