**Release candidate:** Pre-release: 3.3.1 has not yet been released.
RC1: September 23, 2013 RC2: September 27, 2013 3.3.1 is to be a bug fix release in the Puppet 3.3 series. The focus of the release is fixing backwards compatibility regressions that slipped in via the YAML deprecations in 3.3.0. **Upgrade Note** The release of Puppet 3.3.1 will supersede the upgrade warning for Puppet 3.3.0. As of 3.3.1, agent nodes will be compatible with all Puppet 3.x masters with no extra configuration. Puppet 3.3.1-rc2 Downloads ------------------------------------------ Source: https://downloads.puppetlabs.com/puppet/puppet-3.3.1-rc2.tar.gz Available in native package format in the pre-release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For information on how to enable the Puppet Labs pre-release repos, see: http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#enabling-the-prerelease-repos Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.3.1.rc2.gem or by using `gem install --pre puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.3.1-rc2.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.3.1-rc2.msi Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.3.1-rc2: https://projects.puppetlabs.com/projects/puppet/ Fixes for Backwards Compatibility Regressions in 3.3.0 -------------------------------------------------------------------------------- ## Issue 22535: puppet 3.3.0 ignores File ignore in recursive copy ## Issue 22608: filebucket (backup) does not work with 3.3.0 master and older clients ## Issue 22530: Reports no longer work for clients older than 3.3.0 when using a 3.3.0 puppet master ## Issue 22652: ignore doesn't work if pluginsync enabled New backward compatibility issues were discovered after the release of 3.3.0, so we changed our handling of deprecated wire formats. Starting with 3.3.1, you do not need to set additional settings in puppet.conf on your agent nodes in order to use newer agents with puppet masters running 3.2.4 or earlier. Agents will work with all 3.x masters, and they will automatically negotiate wire formats as needed. This behavior supersedes the behavior described for 3.3.0; the report_serialization_format setting is now unnecessary. Additionally, this release fixes two situations where 3.3.0 masters would do the wrong thing with older agents. (Reports would fail unless the master had report_serialization_format set to yaml, which was not intended, and remote filebucket backups would always fail.) Miscellaneous Regression Fixes ----------------------------------------------- ## Issue 22384: Excessive logging for files not found This was a regression in 3.3.0. When using multiple values in an array for the file type's source attribute, Puppet will check them in order and use the first one it finds; whenever it doesn't find one, it will log a note at the "info" log level, which is silent when logging isn't verbose. In 3.3.0, the level was accidentally changed to the "notice" level, which was too noisy. ## Issue 22529: apt package ensure absent/purged causes warnings on 3.3.0 This was a regression in 3.3.0. The apt package provider was logging bogus warnings when processing resources with ensurevalues of absent or purged. ## Issue 22493: Can't start puppet agent on non english Windows This was a regression in 3.2.4, caused by a bug in one of the Ruby libraries Puppet relies on. We submitted a fix upstream, and packaged a fixed version of the gem into the Windows installer. Fixes for Long-Standing Bugs ------------------------------------------- ## Issue 19994: ParsedFile providers do not clear failed flush operations from their queues This bug dates to Puppet 2.6 or earlier. The bug behavior was weird. Basically: Your manifests include multiple ssh_authorized_key resources for multiple user accounts. One of the users has messed-up permissions for their authorized keys file, and their resource fails because Puppet tries to write to the file as that user. All remaining key resources also fail, because Puppet tries to write the rest of them to that same user's file instead of the file they were supposed to go in. ## Issue 21975: Puppet Monkey patch 'def instance_variables' clashing with SOAP Class... This bug dates to 3.0.0. It was causing problems when using plugins that use SOAP libraries, such as the types and providers in the puppetlabs/f5 module. ## Issue 22474: --no-zlib flag doesn't prevent zlib from being required in Puppet This bug dates to 3.0.0, and caused Puppet to fail when running on a copy of Ruby without zlib compiled in. ## Issue 22471: Malformed state.yaml causes puppet to fail runs with Psych yaml parser This bug dates to 3.0.0, and could cause occasional agent run failures under Ruby 1.9 or 2.0. Puppet 3.3.1-rc2 Contributors ------------------------------------------ Andrew Parker, Josh Cooper, Josh Partlow, Kylo Ginsberg, Matthaus Owens, Moses Mendoza, Patrick Carlisle, Rob Braden Puppet 3.3.1-rc2 Changelog ---------------------------------------- Andrew Parker (9): (Maint) Convert to new block expects (#22471) Rescue errors specific to the YAML parser (Maint) Simplify code (Maint) Stop asserting nothingness (#22471) Extract YAML interaction into shared code (#22471) Remove duplication by using Puppet::Util::Yaml (#22384) Log 404 and 406 responses at info (#22530) Support both YAML and PSON (#22652) Parse query strings in rack w/o rack Josh Cooper (8): (Maint) TestHelper already clears global state (Maint) Don't keep Tempfile open while specs are running (Maint) Stop asserting nothingness (Maint) Fixup whitespace (Maint) Remove spurious subproject commit line (#22608) Restore the ability for master to accept pson file backups (Maint) Fix typo in method name (#22652) Restore rack parsing of POST body parameters Josh Partlow (5): (#22529) Dpkg provider does not warn on package not found (#22529) Rpm provider does not parse 'package foo is not installed' as a package (#22529) Acceptance test for puppet package resource behavior (maint) Convert from should to expect syntax (#22529) Update acceptance test for regex fix and solaris Kylo Ginsberg (14): (maint) Fix misspellings in spec tests (#22535) Add puppet version to status indirector (#22535) Revert to yaml when a new agent talks to old master (#22535) Fix apply/etc by setting the status_terminus per application (#22535) Cleanup of desc/hook for new settings (#22535) Improve notice message for backward compatibility (#22535) Add tests for backward compatibility settings (#22535) Add test for legacy yaml serialization of arrays in query string (#22535) Fix an exception msg; cosmetic. (#22535) Fix support for agent's status endpoint (#22535) Make a full status object the default in agent spec tests. (#22535) Use a response header for version (#22652) Add be_one_of matcher (copped from pcarlisle) (#22652) Tighten up spec for multi-valued params in a POST body Matthaus Owens (1): (#22474) Update forge/repository.rb to conditionally include zlib Moses Mendoza (1): (packaging) Update PUPPETVERSION for 3.3.1-rc1 Patrick Carlisle (4): (maint) Don't use subject in parsedfile spec (#19994) Ensure that failed ParsedFile operations are marked flushed (#21975) Don't monkey patch Object#instance_variables (#22471) Finish removing duplication of yaml exceptions Rob Braden (1): (packaging) Update PUPPETVERSION for 3.3.1-rc2 -- Rob Braden Puppet Labs -- 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 puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
