Bug 471918

Summary:	Need assigned User/Group for puppet
Product:	Red Hat Enterprise Linux 5	Reporter:	Robert Rati <rrati>
Component:	setup	Assignee:	Ondrej Vasik <ovasik>
Status:	CLOSED ERRATA	QA Contact:	BaseOS QE <qe-baseos-auto>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.4	CC:	rvokal
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-05-14 07:41:11 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 Robert Rati 2008-11-17 17:18:29 UTC

Description of problem:
We are shipping puppet in MRG, and I am told I need to request uid/gid values for the puppet user.  Currently the package's pre-install script creates the puppet user/group but doesn't specify a uid/gid for either.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Ondrej Vasik 2008-11-17 18:29:21 UTC

Ok, will try to find suitable uid/gid pair for RHEL-5 puppet although number of free uidgid numbers under uidgid 100 is very close to zero.

Comment 2 Ondrej Vasik 2008-11-18 12:18:57 UTC

Just as note, uidgid pair 52:52 is now reserved for puppet in rawhide uidgid file (setup-2.7.4-2.fc11)

Comment 3 Robert Rati 2008-11-18 14:45:52 UTC

IS this uid/gid pair reserved for RHEL4 as well?

Comment 4 Ondrej Vasik 2008-11-18 14:50:17 UTC

Not at the moment, as you know, RHEL-4 and RHEL-5 has different system of updates. But I hope it will get to RHEL-4 soon...

Comment 14 errata-xmlrpc 2009-05-14 07:41:11 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0484.html