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

Russ Allbery rra at debian.org
Thu Nov 27 00:36:44 UTC 2014


Niels Thykier <niels at thykier.net> writes:

> --- a/en/issues.dbk
> +++ b/en/issues.dbk
> @@ -299,25 +299,36 @@ reboot the system.
>  </section>
>  
>  <section id="puppet">
> -<title>Puppet 2.6 / 2.7 compatibility</title>
> -<programlisting condition="fixme">TODO: Do puppet 2.7 and 3.7 have a similar issue?</programlisting>
> +<title>Puppet 2.7 / 3.7 compatibility</title>
>  <para>
> -When upgrading a Puppet managed system from squeeze to wheezy, you
> -must ensure that the corresponding puppetmaster runs at least Puppet
> -version 2.7. If the master is running squeeze's <systemitem
> -role="package">puppetmaster</systemitem>, the managed wheezy system
> -will not be able to connect to it.
> +  If you are using Puppet, please be aware that Puppet 3.7 is not
> +  backwards compatible with Puppet 2.7.  Among other things, the
> +  scoping rules have changed and many deprecated constructs have been
> +  removed.

See the <a
href="https://docs.puppetlabs.com/puppet/3/reference/release_notes.html#puppet-300">Puppet
3.x release notes</a> for some of the changes, although be aware that
there are further changes in 3.7.

>  </para>
>  <para>
> -Such a combination will lead to the following error message during a
> -<command>puppet agent</command> run:
> +  It is recommended that you check the log files of the puppetmaster
> +  for deprecation warnings and resolve all of these before proceeding
> +  with the upgrade.

Maybe instead:

    Checking the log files of your current puppetmaster for deprecation
    warnings and resolving all of those warnings before proceeding with
    the upgrade will make it much easier to complete the upgrade.

> +  Alternatively, testing the manifests with a tool

Alternatively, or additionally, testing...

> +  like <ulink
> +  url="https://github.com/duritong/puppet_catalog_test:">Puppet

Stray colon in the URL.

> +  catelog test</ulink> may also find potential issues prior to the

catalog

Otherwise looks good to me.  Thanks for writing this, Niels!

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



More information about the Pkg-puppet-devel mailing list