Puppet 3.0.0rc3 is a feature release candidate for the 3.x series of Puppet.
Puppet 3.0.0 has breaking changes from the Puppet 2.7 series and has new dependencies of Facter version 2.0.0 or greater, and Hiera (and the hiera puppet functions) version 1.0.0 or greater. Downloads are available at: * Source http://downloads.puppetlabs.com/puppet/puppet-3.0.0rc3.tar.gz RPMs are available at http://yum.puppetlabs.com Debs are available at http://apt.puppetlabs.com Mac packages are available at http://downloads.puppetlabs.com/mac/puppet-3.0.0rc3.dmg Windows packages are available at http://downloads.puppetlabs.com/windows/puppet-3.0.0rc3.msi See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected puppet version of 3.0.0rc3: http://projects.puppetlabs.com/projects/puppet/ ## Puppet 3.0.0rc3 Release Notes ## (#14761) Add boot, reboot to excludes list for redhat provider On sles, the reboot init script would be triggered during a `puppet resource service` call, which would ignore the status argument and proceed to reboot the system. It would also call the boot init script, which could hang the puppet call indefinitely. This commit adds both the boot and reboot services to the redhat provider's exclude list. It also updates the redhat provider spec test to test for those changes. (#14297) Handle upstart services better The previous changes to the upstart provider didn't take into account services that may have upstart jobs in /etc/init with no corresponding symlink to upstart-job in /etc/init.d. This fix adds /etc/init/$service.conf to the search path in the upstart provider. In order to allow upstart to use debian as its parent, this commit adds methods for enabled?, enable and disable. Without this fix, using a debian style init script on ubuntu requires manually specifying the debian provider be used. With this commit, the upstart provider can be the default for ubuntu and still fail up to its parent, debian. The enabled?, disable, and enable methods are complicated because upstart has 3 behaviors to account for. Upstart < 0.6.7 have only the conf file and start on stanzas to worry about, 0.6.7 < upstart < 0.9.0 has a manual stanza which removes any previous start on declaration, and upstart >= 0.9.0 has an override file. In upstart >= 0.9.0, the provider does all of its work using override files to leave the upstart conf file for the service intact and unchanged. Because of the need to know which upstart version is being used, this commit also adds a method and a class variable to hold and access the upstart version, obtained by a call to `initctl --version`. (#14343) Lookup in correct inherited scope The previous twoscope lookup of the inheritied scope tried to find the inherited scope by looking up the class_scope() directly. Unfortunately, this does not work correctly in cases where the inherited scope is qualified to the topscope (::parent) or where the scope is implicitly qualified (class a { class b {} class c inherits b {} }). By using the same mechanism that variables use for looking up scope (the qualified_scope() method) variable lookup will find a scope consistent with what qualified variable lookups will find. (#14615) Exclude helperscripts in gentoo service provider The directory `/etc/init.d` does not only store normal initscripts but also a few helper scripts (like `functions.sh`). The former behaviour was to treat them as regular initscripts which can lead to dangerous results especially when running `puppet resource service`. This command will issue `/etc/init.d/<script> status` on every script inside `/etc/init.d`. Because the helperscripts don't care about arguments, this will cause the system to reboot when `/etc/init.d/reboot.sh status` is executed. Exclude helperscripts when searching inside `/etc/init.d`. ## Puppet 3.0.0rc3 Changelog ## Andrew Parker (5): 2d83e22 (Maint) Added test for fully qualified variables 3541db6 (#14343) Lookup in correct inherited scope 36c41e1 (#14343) Test cases for more forms of variable lookup 55505db (Maint) Fix upstart provider to work on Ruby 1.9.3 c0cb0fa (Maint) Close filehandles after read in upstart Daniel Pittman (1): 37df5c4 (#14615) Final stub fixes for the tests. Hailee Kenney (2): 6be09f0 (#3909) Strip trailing dot from default FQDN 6c37538 (#3909) Move default certname logic to Puppet::Settings Jeff Weiss (2): 2ec9b74 (maint) Make Puppet have hard dependency on Facter 2.0 2864d86 (maint) Change Facter dep from exit to raise Matthaus Litteken (13): 91827e8 (#14297) Handle upstart services better b9ed026 (#14297) Update spec tests for upstart provider 6cca061 (#14297) Add acceptance test for upstart provider 3c5ef40 (#14297) Clean up upstart provider and tests f5d1f74 (#14297) Update upstart provider acceptance tests 466ab49 (#14297) Define agent in upstart acceptance test a45942b (#14297) Don't remove tty1 or rsyslog during upstart acceptance d19f93f Update redhat init scripts to use `puppet (agent|queue|master)` 6e2f23d Update puppet gem dependencies b0f1d58 Update redhat.spec dependency to include hiera-puppet 7c1d8c2 (maint) Disable upstart spec test on windows e619304 (#14761) Add boot, reboot to excludes list for redhat provider d58a7cc Updating CHANGELOG, conf/redhat/puppet.spec for 3.0.0rc3 Moses Mendoza (2): cfeb013 Update CHANGELOG puppet.spec for 2.7.15rc2 20c3da3 Update CHANGELOG, conf/redhat/puppet.spec for 2.7.15rc3 Stefan Schulte (3): 0788ea2 (#14615) Exclude helperscripts in gentoo service provider 060810e maint: Make it easier to test the service provider f11dfd6 (#14615) Fix provider spec tests to work on non gentoo systems -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
