Bug 797415

Summary:	glassfish-jaf giving error during installation in kickstart
Product:	Red Hat Satellite	Reporter:	Forrest Taylor <ftaylor>
Component:	Packaging	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED UPSTREAM	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.1	CC:	cpelland, jsherril, mmccune
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-19 18:12: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:

Description Forrest Taylor 2012-02-25 17:39:35 UTC

I have setup a repository for System Engine and I install katello-all in kickstart.  During the installation, I see an error when installing glassfish-jaf:

Installing glassfish-jaf-1.1.0-9.el6.noarch
/var/tmp/rpm-tmp.AXfWcZ: line 4: cat: command not found

This error likely comes from the postinstall scriptlet:

rpm -q --scripts glassfish-jafpostinstall scriptlet (using /bin/sh):

echo -e "<dependencies>\n" > /etc/maven/maven2-depmap.xml
if [ -d /etc/maven/fragments ] && [ -n "`find /etc/maven/fragments -type f`" ]; then
cat /etc/maven/fragments/* >> /etc/maven/maven2-depmap.xml
fi
echo -e "</dependencies>\n" >> /etc/maven/maven2-depmap.xml
...

I also ran into other package issues installing in kickstart (see bug#795600 and bug#795602).

Comment 1 Forrest Taylor 2012-03-02 02:49:41 UTC

Just tested 2012-03-01.1 code drop.
katello-all-0.1.301-2.el6.noarch
glassfish-jaf-1.1.0-9.el6.noarch

I still have the same issue installing in kickstart

Comment 2 Justin Sherrill 2012-03-16 17:35:42 UTC

going by  https://bugzilla.redhat.com/show_bug.cgi?id=795602  i think just adding  coreutils as a Requires(post)  should do it.

Tried adding this and rebuilding in brew, but hit a build issue.  Gonna have to talk with a release engineer to sort it out.

Comment 4 Mike McCune 2013-08-16 18:22:19 UTC

getting rid of 6.0.0 version since that doesn't exist

Comment 5 Mike McCune 2013-09-19 18:12:11 UTC

These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM.  If this is a mistake feel free to re-open.