Bug 659367

Summary:	puppet package is outdated
Product:	[Fedora] Fedora EPEL	Reporter:	Luc de Louw <luc>
Component:	puppet	Assignee:	Jeroen van Meeuwen <vanmeeuwen+fedora>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	el6	CC:	k.georgiou, tmz, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-18 18:58:42 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Luc de Louw 2010-12-02 16:32:22 UTC

Description of problem:
The package of Puppet in EPEL6-beta is outdated, 0.25.5 vs. upstream 2.6.3.


Version-Release number of selected component (if applicable):
0.25.5

How reproducible:
Always

Steps to Reproduce:
1. yum list puppet
  
Actual results:
0.25.5-1.el6


Expected results:
2.6.3-2

Additional info:
There is a spec file in upstreams tarball, it easily builds and works on RHEL5 and F14. (RHEL6 no yet tested).

It would be great to have a more up to date RPM for EPEL6

Comment 1 Todd Zullinger 2010-12-02 16:49:29 UTC

See http://tmz.fedorapeople.org/repo/puppet/

We need help from folks updating from 0.25.5 to 2.6.4 and reporting any regressions.  That's the reason that we have not pushed 2.6.x into Fedora or EPEL yet.  If we were to do this for just EL-6 or F-14, it would make it hard for people running masters on older releases, since puppet really wants the master to be as new or newer than the clients.

Comment 2 Luc de Louw 2010-12-02 21:48:28 UTC

Dead Todd,

We've just upgraded from EPEL5's puppet 0.25.5 a to custom 2.6.3 build (on RHEL5). At the moment we have now only a experimental installation for a PoC. We'd like to change that with the deployment of RHEL6.

The only problem so far was that we needed to delete all SSL related stuff on the clients as this was reported on several mailing lists.

Please let me know if and how we can help to get 2.6.x to EPEL6.

In doubt, please consider to release both versions such as RHEL5 contains postgresql and postgreql84.

Thanks,

Luc

Comment 3 Todd Zullinger 2010-12-02 22:15:30 UTC

I've seen folks have problems with ssl on nearly any version of puppet.  I'm not aware of any known issue specific to moving from 2.6.x though.  If there were and it was required to remove and recreate all ssl certs, there's no way we'd even consider updating puppet in EPEL.

I'm not interested in trying to maintain both puppet 0.25.x and 2.6.x versions either.  I don't know that it's even possible without significant hacks to make both versions parallel installable.

What custom build are you using?  Are they based on the rpms that I have provided or the spec file from the puppet tarball?  If neither, then I'm afraid the testing doesn't help tell us a lot.  If they are though, what changes have you made?

Comment 4 Todd Zullinger 2011-03-18 18:58:42 UTC

puppet-2.6.6-1 will be heading to epel-testing shortly for both EL-5 and EL-6 (along with the Fedora branches).

*** This bug has been marked as a duplicate of bug 666094 ***