Bug 1190040

Summary:	Warnings (user/group tomcat doesn't exist) messages while installing 'gutterball' rpm from 6.1 compose
Product:	Red Hat Satellite	Reporter:	Sachin Ghai <sghai>
Component:	Installation	Assignee:	Devan Goodwin <dgoodwin>
Status:	CLOSED ERRATA	QA Contact:	jcallaha
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	Unspecified	CC:	bbuckingham, dgoodwin, jcallaha, jmontleo, sthirugn
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-12 05:23:43 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:
Bug Depends On:
Bug Blocks:	1193969

Description Sachin Ghai 2015-02-06 07:24:49 UTC

Description of problem:
while installing 'gutterball' rpm, getting following warning messages 

 Installing : gutterball-1.0.10-1.el6.noarch                                                                                                 224/434 
warning: user tomcat does not exist - using root
warning: group tomcat does not exist - using root
warning: user tomcat does not exist - using root
warning: group tomcat does not exist - using root
warning: user tomcat does not exist - using root
warning: group tomcat does not exist - using root
warning: user tomcat does not exist - using root
warning: group tomcat does not exist - using root
warning: user tomcat does not exist - using root
warning: group tomcat does not exist - using root
warning: user tomcat does not exist - using root
warning: group tomcat does not exist - using root
warning: user tomcat does not exist - using root
warning: group tomcat does not exist - using root
warning: user tomcat does not exist - using root
warning: group tomcat does not exist - using root
...


Version-Release number of selected component (if applicable):
Satellite 6.1.0 Beta Snap 1 Compose 3

How reproducible:


Steps to Reproduce:
1. Install Sat6 6.1 Beta Snap 1 Compose 3
2.
3.

Actual results:
 Installing : gutterball-1.0.10-1.el6.noarch                                                                                                 224/434 
warning: user tomcat does not exist - using root
warning: group tomcat does not exist - using root
warning: user tomcat does not exist - using root
warning: group tomcat does not exist - using root
warning: user tomcat does not exist - using root
warning: group tomcat does not exist - using root
warning: user tomcat does not exist - using root
warning: group tomcat does not exist - using root
warning: user tomcat does not exist - using root

Expected results:
no warning should be listed repeatedly. looks ugly

Additional info:

Comment 2 Sachin Ghai 2015-02-11 09:43:09 UTC

In sat6.1.0 beta snap2 too same warnings appears.

Comment 3 Adam Price 2015-02-17 19:11:10 UTC

also present on compose3.

as a side-effect this is causing permission errors on gutterball. specifically when it tries to create its logfile. it results in a access denied error and gutterball halts.

Comment 4 Devan Goodwin 2015-02-17 19:56:06 UTC

Gutterball has no dependency on tomcat, big oversight, only functional because candlepin happens to be on the same system and thus it ends up installed eventually, but not at the point where gutterball is installing.

Simple fix, in process now, will rebuild asap.

Comment 5 Devan Goodwin 2015-02-17 20:16:57 UTC

Built as gutterball-1.0.12-1 in katello-koji and brew. Will notify sat6 lists to recompose.

Comment 8 jcallaha 2015-02-26 18:42:08 UTC

Verified in Satellite 6.1.0 snap 4 compose 2.

Version tested:
RHEL 66
RHEL 71

Comment 9 Bryan Kearney 2015-08-11 13:33:54 UTC

This bug is slated to be released with Satellite 6.1.

Comment 10 errata-xmlrpc 2015-08-12 05:23:43 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2015:1592