Bug 765579 (GLUSTER-3847) - cannot install glusterfs-core with rpm. (scriptlet failed exit status 127)
Summary: cannot install glusterfs-core with rpm. (scriptlet failed exit status 127)
Keywords:
Status: CLOSED WORKSFORME
Alias: GLUSTER-3847
Product: GlusterFS
Classification: Community
Component: build
Version: pre-release
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-06 08:16 UTC by Steve Yong
Modified: 2013-12-19 00:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-17 18:48:03 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Steve Yong 2011-12-06 08:16:38 UTC
os : centos 5.5
kernel : 2.6.18-194.3.1
arch : x86_64


I'm trying to install glusterfs with rpms.
I downloaded rpms from 
http://download.gluster.com/pub/gluster/glusterfs/3.2/LATEST/CentOS/5.7/
(I only can find centos version 5.7 and 6.0 I could not find 5.5 in that site)

and I try to install "glusterfs-fuse-3.2.5-1.x86_64.rpm"

and copy it to my local repository, and run "createrepo"

after that I install glusterfs-core with "yum".

during the installation, 
the error message shows,


===========================================================================
Installing     : glusterfs-core               

/var/tmp/rpm-tmp.6336: line 25: sleep: command not found
error: %post(glusterfs-core-3.2.5-1.x86_64) scriptlet failed, exit status 127

===========================================================================

what is the problem? 

if you need more information, please let me know.

Comment 1 Amar Tumballi 2012-04-17 18:48:03 UTC
We fixed many issues with RPM packaging in 3.3.0 version, a beta tarball/rpm sets are out now, can you please confirm the behavior now? I fix it as worksforme, because we are not able to see this locally here.


Note You need to log in before you can comment on or make changes to this bug.