The update to puppet-2.6.6 brings a large number of bug fixes and several new language features. As is typical with puppet version bumps, it is recommended to update the puppetmaster before updating the clients.
For details on what's changed, refer to the upstream release notes:
http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes
(This update includes several of the fixes for regressions which are included in puppet-2.6.7rc1.)
Please login to add feedback.
This update has been submitted for testing by tmz.
This update has been pushed to testing
This breaks production installs of puppet that are integrated into Passenger. It requires manual changes to config.ru to recover. These incompatible changes do not seem appropriate for EPEL 5 according to the EPEL Guidelines. At the very least, I would expect such disruptive changes to be released in Fedora for a while before being released in EPEL, not at the same time.
Sorry for the trouble. Unfortunately, passenger isn't in Fedora or EPEL and thus is not officially supported. We release puppet across both Fedora and EPEL at the same time because the master is generally required to be newer than the clients and more folks run masters on EL systems than on Fedora. It's not an ideal situation, but this is as it has always been with puppet. https://bugzilla.redhat.com/683229 was filed regarding the stock config.ru files. Interested folks are encouraged to work upstream to make the example configs accurate for Fedora/EL.
Works for me thus far, thanks for the update.
Working for me with two puppetmasters and around 60 or so clients with a variety of different recipes.
Strange guesswork of the new puppet: 1. Apr 1 15:28:29 sysmgmt puppet-master[21542]: You have configuration parameter $classfile specified in [puppetd], which is a deprecated section. I'm assuming you meant [agent] 2. Apr 1 15:28:29 sysmgmt puppet-master[21542]: You have configuration parameter $report specified in [puppetd], which is a deprecated section. I'm assuming you meant [agent] 3. Apr 1 15:28:29 sysmgmt puppet-master[21542]: You have configuration parameter $server specified in [puppetd], which is a deprecated section. I'm assuming you meant [agent] 4. Apr 1 15:28:29 sysmgmt puppet-master[21542]: You have configuration parameter $localconfig specified in [puppetd], which is a deprecated section. I'm assuming you meant [agent] 5. Apr 1 15:28:29 sysmgmt puppet-master[21542]: You have configuration parameter $graph specified in [puppetd], which is a deprecated section. I'm assuming you meant [agent] 6. Apr 1 15:28:29 sysmgmt puppet-master[21542]: You have configuration parameter $reports specified in [puppetmasterd], which is a deprecated section. I'm assuming you meant [master]
The messages are telling you that the configuration sections (i.e. [puppetd] have changed to use the new application names (i.e. [agent]). The old section names continue to work but should be changed in your config at your convenience.
sorry, not so strange.. I was reading it guessing $classfile meant [agent], but obviously it's section [puppetd] that's being changed to [agent]. I'm giving it +1 for now, as it seems to be working on our lab puppetmaster. Will roll it out to the clients as well soonish.
This update has reached 14 days in testing and can be pushed to stable now if the maintainer wishes
light testing looks ok
Both puppetmaster and client work for me.
Seems fine with my configuration.
No problems here (master for 100 or so clients)
This update has been submitted for stable by tmz.
This update has been pushed to stable