Puppet 3.0.2-rc2 is a bugfix release candidate for the 3.x series of Puppet. This release candidate fixes bugs #15929, #17624, #18046, and #18047. To see a list of the issues addressed by this release, check out the 3.0.2 version in our issue tracter at: https://projects.puppetlabs.com/versions/337
Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.0.2-rc2.tar.gz RPMs are available at https://yum.puppetlabs.com Debs are available at https://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.0.2.rc2.gem or by using `gem install --pre puppet` Mac packages are available at https://downloads.puppetlabs.com/mac/puppet-3.0.2-rc2.dmg Windows packages are available at https://downloads.puppetlabs.com/windows/puppet-3.0.2-rc2.msi Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.0.2-rc2: https://projects.puppetlabs.com/projects/puppet/ ============================ ## Puppet 3.0.2-rc2 Release Notes ## ============================ #15929, #17624 Handle malformed plists Previously, if launchd encountered a plist that did NOT have a 'label' key, or a malformed plist that plutil couldn't read, Puppet would throw a stacktrace or log a nebulous error that looked like: `Error: Could not run: No resource and no name in property hash in launchd instance` That was not ideal. This commit will catch the situation where a plist is missing a 'label' key Puppet is skipping the plist. It will also catch the case the where a plist is malformed and plutil cannot read it. With either condition, the commit adds code that logs a Puppet.warning and skips the malformed plist gracefully. #18046 Enable rubygems support Previously, puppet used to require rubygems, but this broke environments that didn't use rubygems. The decision to require rubygems was moved out of puppet and into the code that loads puppet. This was done for daemon.bat, but not for the other scripts, e.g. puppet.bat. This commit enables rubygems support in the environment.bat file which all of the other bat files source. #18047 Revert change to user confdir In 3.0, the default user confdir (and vardir) was changed from ~/.puppet to the Dir::LOCAL_APPDATA/PuppetLabs. However, when puppet is run as a non-administrator, puppet will attempt to create its confdir, e.g. C:\Users\albert\AppData\Local\PuppetLabs\puppet, and fail because the parent PuppetLabs directory doesn't exist. This wasn't an issue in 2.7.x, because the confdir was ~/.puppet, so the parent directory always existed. This commit restores the previous behavior for non-administrators. No changes are required for administrators, because the MSI installer creates the necessary directories within COMMON_APPDATA. ========================= ## Puppet 3.0.2-rc2 Changelog ## ========================= Gary Larizza (11): b708a41 Optimize calls for operating system version cb682bd Wrap ShadowHashData setting into its own method a0e4d13 Wrap user plist retrieval into get_users_plist() 9ff9a80 Do not fail if ShadowHashData doesn't exist 297e93d Provide wrapper method for new StringIO objects b0a05e8 Create base64_decode_string 4338d99 Clean up comments a925d45 Update spec tests 4a1bc10 Update Documentation to YARD standard 16d2d9a [15929] [17624] Handle malformed plists f432447 Update launchd test for 1.9.3 Jeff McCune (1): 74daa17 (Maint) Add YARD tags to return_globbed_list_of_file_paths method Josh Cooper (1): 48e6801 (#18047) Revert change to user confdir Matthaus Owens (1): 81ca2a7 Update PUPPETVERSION to 3.0.2-rc2 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
