Description of problem:
The 2.6.x release series was released in July, and seems reasonably stable. Any chance of pushing this to F-14 and rawhide? Also, what are your thoughts on pushing this for EPEL 5? In my limited testing, compatibility seems good, though I have to admit I switched to using 2.6 pretty soon after it was released and didn't use 0.25.5 very much.
We've held off pushing this to any Fedora releases until we're ready to push it to EPEL as well, since many many folks run puppet masters on EL and clients on Fedora.
The biggest thing we need is testing from 0.25.x setups to 2.6.x and confirmation that the update is indeed compatible. I have provided 2.6.x builds for Feodra and EPEL at http://tmz.fedorapeople.org/repo/puppet/ since 2.6.x was in beta and have solicited feedback on the puppet lists and IRC. The relatively little feedback I've received has been mostly positive, but not sufficient to make me comfortable to push 2.6.x into epel-testing quite yet. I do think 2.6.4 is pretty close, but more testing from folks who have successfully (and cleanly) upgraded from 0.25.5 to 2.6.4 would be very helpful.
Sadly, it seems many folks just consume the packages and leave us hanging as maintainers. I fear that when we do eventually push 2.6.x into epel-testing and fedora we will find folks upgrading and complaining of minor incompatibilities that should have been caught by folks testing the various release candidates during the past 6 months. :(
Any more progress on this? I'm just getting started with puppet and I'd like to start with up to date versions. Not much help with the upgrade I'm afraid though.
Yes. I'll be pushing 2.6.6 into fedora and epel testing repositories in the next day or two, assuming no show-stopper bugs are found¹.
¹ I planned this with 2.6.5 a few weeks ago and the day after it was released
some ugly regressions were found, necessetating 2.6.6. Hence my desire to let
the newst code simmer for a few days. :)
*** Bug 659367 has been marked as a duplicate of this bug. ***
puppet-2.6.6-1.fc14 has been submitted as an update for Fedora 14.
puppet-2.6.6-1.el5 has been submitted as an update for Fedora EPEL 5.
puppet-2.6.6-1.fc15 has been submitted as an update for Fedora 15.
puppet-2.6.6-1.fc13 has been submitted as an update for Fedora 13.
puppet-2.6.6-1.el6 has been submitted as an update for Fedora EPEL 6.
Any chance of a package update on this? It's been 6 months since the 2.6.6 release of puppet.
The 2.6 release had been updated to 2.6.9 by June, since when work has clearly concentrated on the 2.7 release.
The 2.7 release itself has now been updated to 2.7.3.
Puppet will be an integral part of the Katello project. It would be nice to be able to run one of the more recent Puppet releases.
It's just a thought.
The 2.6.6 packages have been in fedora and epel testing repos for a long time now. The last thing blocking us now is SELinux policy on EL-6. I've tried to find out when this will be pushed in RHEL but have had no luck. Anyone with contacts inside Red Hat that could give some insight would be great.
I'm soon going to push this to stable and just not on epel-announce that anyone running with SELinux in enforcing mode should get updated slinux-policy packages from Dan Walsh's people.redhat.com repo or set it to permissive until RHEL updates that package.
As far as upstream and 2.7, there are a number of changes that have the potential to cause users troubles. An upgrade will require determining whether these changes are reasonable to expect in a stable update.
A few that come to mind:
* Variable scoping. Puppet 2.7 issues deprecation warnings for dynamic variable and resource defaults lookup. More details are at http://docs.puppetlabs.com/guides/scope_and_puppet.html .
* The hasstatus parameter in the service resource type now defaults to true. In general, this is a good thing, since nearly all initscripts in EL/EPEL have a status option. But, this change could break existing manifests.
* The --parseonly option to puppet has been removed and replaced with puppet parser validate. The latter has slightly different semantics and output, I've been told. I spoke with Michael Stahnke from Puppetlabs and it may be worth filing this as a bug upstream. It's possible that they'll restore --parseonly to retain compatibility. One of the reasons it was dropped is that it sometimes reported success when it should have failed, so folks relying on it now are suffering from implementation bugs.
Todd - thanks as ever for your work on this. One thought though - if you're intending to push a 2.6 series update to stable, wouldn't it be worth considering pushing 2.6.9 which fixes a number of the 2.6.6 bugs? I realize 2.6.6 has had a lot of testing over the past few months and so one could argue that's a safer bet for stable, but in my experience, the 2.6.9 release was a drop in replacement for 2.6.6.
At this point, I don't want to negate the testing that 2.6.6 has received and introduce new bugs with 2.6.9. I have 2.6.9 packages in my fedorapeople repo and as soon as 2.6.6 is moved to stable, 2.6.9 can go to testing, where it shouldn't required too long to be proven.
puppet-2.6.6-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
puppet-2.6.6-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
puppet-2.6.6-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
puppet-2.6.6-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.