Description of problem: On installing RHSS using RHSS-3.0-20140617.n.0-RHS-x86_64-DVD1.iso , the following error is observed in the /root/install.log Installing lvm2-libs-2.02.100-8.el6.x86_64 Installing lvm2-2.02.100-8.el6.x86_64 Installing glusterfs-server-3.6.0.18-1.el6rhs.x86_64 error reading information on service glusterfsd: No such file or directory Installing cryptsetup-luks-libs-1.2.0-7.el6.x86_64 Installing cryptsetup-luks-1.2.0-7.el6.x86_64 Installing libsmbclient-3.6.9-168.3.el6rhs.x86_64 Version-Release number of selected component (if applicable): RHSS-3.0-20140617.n.0-RHS-x86_64-DVD1.iso How reproducible: Steps to Reproduce: 1. Install RHSS using RHSS-3.0-20140617.n.0-RHS-x86_64-DVD1.iso 2. Examine the /root/install.log file Actual results: The /root/install.log file shows that errors were reported during package installation, for RHSS installation using ISO. Expected results: There should be no errors during package installation for RHSS installation using ISO. Additional info:
Reassigning to Bala. Appears to be an issue in glusterfs-server package.
This is also duplicate of bz#1109111
The spec file has fix like below ie glusterfsd service is started if its available if [ -f %_init_glusterfsd ]; then %_init_enable glusterfsd fi
On installing RHGS-3.1 using RHGSS-3.1-20150629.n.0-RHS-x86_64-DVD1.iso, the reported error is no longer observed in the /root/install.log ##### Installing glusterfs-libs-3.7.1-6.el6rhs.x86_64 Installing glusterfs-3.7.1-6.el6rhs.x86_64 Installing glusterfs-client-xlators-3.7.1-6.el6rhs.x86_64 Installing glusterfs-api-3.7.1-6.el6rhs.x86_64 Installing glusterfs-fuse-3.7.1-6.el6rhs.x86_64 Installing glusterfs-cli-3.7.1-6.el6rhs.x86_64 Installing glusterfs-server-3.7.1-6.el6rhs.x86_64 Installing glusterfs-geo-replication-3.7.1-6.el6rhs.x86_64 Installing glusterfs-rdma-3.7.1-6.el6rhs.x86_64 Installing glusterfs-ganesha-3.7.1-6.el6rhs.x86_64 Installing python-gluster-3.7.1-6.el6rhs.x86_64 ###### Marking as Verified
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://rhn.redhat.com/errata/RHSA-2015-1495.html