Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1095985

Summary:	Puppet versions to be aligned between client and Foreman (proxy) server
Product:	Red Hat OpenStack	Reporter:	Gilles Dubreuil <gdubreui>
Component:	puppet	Assignee:	Mike Burns <mburns>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jaroslav Henner <jhenner>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0 (RHEL 7)	CC:	aberezin, lhh, markmc, mburns, mlopes, morazi, ohochman, rhos-maint, sclewis, yeylon
Target Milestone:	rc
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	puppet-3.6.2-1.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-12 20:20:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gilles Dubreuil 2014-05-09 02:53:19 UTC

Puppet versions must be the same between clients (puppet agent) and puppet master, including when using foreman/foreman-proxy.

On the server side, from latest Foreman repo:
puppet-3.3.2-2.el6.noarch.rpm @rhos-foreman/6.0/latest/foreman/x86_64/os/Packages/

Although, RHEL7's puppet version available at the moment through EPEL7, is too recent, the version provided via RHELOSP 5 is closer but still not aligned:

puppet-3.5.1-1.el7.noarch.rpm @epel/beta/7/x86_64/
puppet-3.4.3-1.el7.noarch.rpm @rhelosp-5.0-el7

Even though Puppet 3.4.3 seems to be working against puppet 3.3.2 without generating errors, this is not supported as there could be bad side effects down the track.

RHOS 5 needs to provide the same version as used on Foreman side.

Comment 2 Gilles Dubreuil 2014-06-06 06:35:55 UTC

If not aligned with same version, the recommendation is to always have the master version higher than the puppet agents.

Obviously to avoid unsupported features to be triggered by the agent.

Comment 4 Gilles Dubreuil 2014-06-06 13:25:16 UTC

Hiera versions needs to be aligned too!

During integration of puppet-gluster for RHEL7 (RHOS5), which requires hiera, I discovered the hiera versions are also not aligned. This along the puppet version mismatch was breaking the catalog execution with following error:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error NameError: uninitialized constant 

Updating to hiera-1.3.1-1.el6 version on the Foreman server addressed the issue.

Comment 5 Mike Orazi 2014-06-06 18:29:15 UTC

Moving to distribution component.

Comment 8 Mike Burns 2014-06-26 15:16:02 UTC

Decision is to use current satellite versions which are higher than both el6 and el7 versions currently.