Description of problem: ========================= On RHSS-3.0 , the "glusterd" service is not started automatically when we reboot the systems. In RHS 3.0: postinstall scriptlet (using /bin/sh): # Legacy server /sbin/chkconfig --add glusterd ;/sbin/chkconfig --add glusterfsd ; Version-Release number of selected component (if applicable): ================================================================= [root@king ~]# gluster --version glusterfs 3.5qa2 built on Mar 26 2014 06:21:25 How reproducible: Steps to Reproduce: ===================== 1. Installed the "RHSS-3.0-20140326.n.5 RHS x86_64" ISO from beaker. 2. After successful installation/reboot , the glusterd service is not started automatically. Actual results: ===================== [root@king ~]# gluster v info Connection failed. Please check if gluster daemon is operational. [root@king ~]# [root@king ~]# [root@king ~]# [root@king ~]# [root@king ~]# service glusterd status glusterd is stopped [root@king ~]# [root@king ~]# chkconfig | grep glusterd glusterd 0:off 1:off 2:off 3:off 4:off 5:off 6:off [root@king ~]# Expected results: ==================== "glusterd" should start automatically after reboots.
The post-install script of glusterfs-server package had the following for RHS 2.1u2 ----------------------------------------------- postinstall scriptlet (using /bin/sh): # Legacy server #/sbin/chkconfig --add glusterd ;#/sbin/chkconfig --add glusterfsd ;/sbin/chkconfig --add glusterd /sbin/chkconfig glusterd on ----------------------------------------------- while for RHS 3.0 it is as follows ----------------------------------------------- postinstall scriptlet (using /bin/sh): # Legacy server /sbin/chkconfig --add glusterd ;/sbin/chkconfig --add glusterfsd ; -----------------------------------------------
Patch is under review at http://review.gluster.org/7432
Verified this on build : root@fan [May-13-2014-11:26:10] >gluster --version glusterfs 3.6.0 built on May 10 2014 13:57:11 Bug is fixed. Moving the bug to verified state.
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. http://rhn.redhat.com/errata/RHEA-2014-1278.html