Red Hat Bugzilla – Bug 813558
puppet 2.6 is broken, time to update to 2.7?
Last modified: 2012-05-16 01:21:06 EDT
Description of problem:
# puppet agent --test
/usr/share/ruby/vendor_ruby/puppet/util/log/destinations.rb:99: warning: class variable access from toplevel
/usr/share/ruby/vendor_ruby/puppet/application/kick.rb: /usr/share/ruby/vendor_ruby/puppet/application/kick.rb:105: Invalid next (SyntaxError)
Version-Release number of selected component (if applicable):
I think it's time to bite the bullet and update to 2.7 everywhere. I have been running a 2.7.12 master for a while against the 2.6.14 clients and haven't had any problems yet. Will start testing with 2.7 clients on Fedora 15, 16, and 17.
The biggest thing that needs tested is compatibility with existing manifests. If we update and there are a lot of new warnings or worse, things that break, it's going to be a big pain.
But we do have to update to 2.7 at least in Fedora >= 17. Unfortunately, even with 2.7, upstream does not recommend ruby 1.9.3, so there are going to be bugs that remain.
Bah, first problem - I seem to be hitting http://projects.puppetlabs.com/issues/9084 so I can't get an initial cert setup for a machine with 2.7.12 on F17.
But no problem with my manifests yet.
scp puppet:/var/lib/puppet/ssl/certs/ca.pem /var/lib/puppet/ssl/certs/ca.pem
ln -s /var/lib/puppet/ssl/certs/ca.pem $(openssl version -d|cut -d\" -f2)/certs/$(openssl x509 -hash -noout -in /var/lib/puppet/ssl/certs/ca.pem).0
Alternate (centos 6.2?):
ln -s /var/lib/puppet/ssl/certs/ca.pem $(openssl version -d|cut -d\" -f2)/certs/$(openssl x509 -subject_hash_old -noout -in /var/lib/puppet/ssl/certs/ca.pem).0
Another reason to want 2.7.x would be the native systemd service support that looks to have went in 2.7.4.
puppet-2.7.13-1.fc17 has been submitted as an update for Fedora 17.
puppet-2.7.13-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
Any chance we can get 2.7.x on EPEL6 as well?
Not in the immediate future, no. There are issues of compatibility with 2.6 and open issues regarding the speed of catalog compilation in 2.7. It's not just a simple yum update and I would rather not cause users trouble. I wish it were simpler to push such updates.