Am Montag, 26. August 2013 12:29:17 UTC+2 schrieb Stig Sandbeck Mathisen: > > maling list <[email protected] <javascript:>> writes: > > > It would be nice to be able to prepare for the most problem - before - > > breaking the setup. > > > > Does anybody has more experiences on this issue. > > Seriously. Check your syslog _before_ upgrading. New features, scope > changes, and other potential problems are marked as "will be deprecated > in the next major release" in the syslog. Apart from that, read the > release notes. > > Apart from that, I hope you've already done the following: > > Read the release notes in the puppet documentation regarding upgrading. > Follow the steps described. > > Upgrade your puppet master to the latest available patch release of your > current version of puppet. Deprecation warnings may have been added. > Check syslog again after running a few agents. > > Copy your current puppet master to a virtual server, snapshot it, and > upgrade it. Point test clients to it, and see what breaks. Rollback to > the snapshot, fix the problem in a hopefully > compatible-with-the-old-release way, and try again. > > If you're completely stuck, ask on the puppet user mailing list. :) >
I already read some of the official puppet docs concering upgrading but I didn't find anything which lists possible syntax changes or describes what could not work anymore in version 2.7. Thanks for the hint. I wasn't aware of the "will be deprecated in the next major release" messages in syslog. I'll check that. I think I also won't get around testing on virtual machines. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
