Description of problem: Re-install fails (clean install untested) if glusterd is running when reinstall starts. reinstall succeeds only after executing "service glusterd stop" on host Version-Release number of selected component (if applicable): all hosts & engine running on Centos 6.5, just updated storage: glusterfs ovirt-engine 3.3.0.1-1.el6 ovirt-engine-lib 3.3.2-1.el6 ovirt-host-deploy.noarch 1.1.3-1.el6 How reproducible: always Steps to Reproduce: 1. start with host "up" 2. put host into "maintenance" 3. click GUI "reinstall" link 4. GUI has message "Host installation failed. Fix installation issues and try to Re-Install" 5. GUI "Events" shows: Host office2a installation failed. Command returned failure code 1 during SSH session 'root.65.2'. Installing Host office2a. Stage: Termination. Installing Host office2a. Retrieving installation logs to: '/var/log/ovirt-engine/host-deploy/ovirt-20140126122137-10.41.65.2-6075adb2.log'. Installing Host office2a. Stage: Pre-termination. Failed to install Host office2a. Failed to execute stage 'Closing up': Command '/sbin/service' failed to execute. Installing Host office2a. Starting gluster. Actual results: 1. GUI has message "Host installation failed. Fix installation issues and try to Re-Install" 2. GUI "Events" shows: Host office2a installation failed. Command returned failure code 1 during SSH session 'root.65.2'. Installing Host office2a. Stage: Termination. Installing Host office2a. Retrieving installation logs to: '/var/log/ovirt-engine/host-deploy/ovirt-20140126122137-10.41.65.2-6075adb2.log'. Installing Host office2a. Stage: Pre-termination. Failed to install Host office2a. Failed to execute stage 'Closing up': Command '/sbin/service' failed to execute. Installing Host office2a. Starting gluster. Expected results: Host in "up" condition Additional info: 2 hosts, separate engine
Attaching /var/log/ovirt-engine/host-deploy/ovirt-20140126122137-10.41.65.2-6075adb2.log will be wise.
Created attachment 855721 [details] host install log Attaching host re-install log
(In reply to Ted Miller from comment #2) > Created attachment 855721 [details] > host install log > > Attaching host re-install log Thanks. 2014-01-26 12:21:37 DEBUG otopi.plugins.otopi.services.rhel plugin.executeRaw:366 execute: ('/sbin/service', 'glusterd', 'stop'), executable='None', cwd='None', env=None 2014-01-26 12:21:37 DEBUG otopi.plugins.otopi.services.rhel plugin.executeRaw:383 execute-result: ('/sbin/service', 'glusterd', 'stop'), rc=1 2014-01-26 12:21:37 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:441 execute-output: ('/sbin/service', 'glusterd', 'stop') stdout: Stopping glusterd:[ OK ] 2014-01-26 12:21:37 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:446 execute-output: ('/sbin/service', 'glusterd', 'stop') stderr: service glusterd stop is failing although should always return 0, unless stop is actually failing. please update the gluster version you actually use.
(In reply to Alon Bar-Lev from comment #3) > please update the gluster version you actually use. yum list installed gluster* Loaded plugins: fastestmirror, presto, priorities, security Loading mirror speeds from cached hostfile * base: mirror.wiredtree.com * epel: epel.mirror.constant.com * extras: centos.mbni.med.umich.edu * updates: mirror.wiredtree.com Installed Packages glusterfs.x86_64 3.4.2-1.el6 @glusterfs-epel glusterfs-api.x86_64 3.4.2-1.el6 @glusterfs-epel glusterfs-cli.x86_64 3.4.2-1.el6 @glusterfs-epel glusterfs-fuse.x86_64 3.4.2-1.el6 @glusterfs-epel glusterfs-libs.x86_64 3.4.2-1.el6 @glusterfs-epel glusterfs-rdma.x86_64 3.4.2-1.el6 @glusterfs-epel glusterfs-server.x86_64 3.4.2-1.el6 @glusterfs-epel
Observation: Seems to be a glusterfs problem on host [root@office2a ~]$ service glusterd stop [root@office2a ~]$ [ OK ] [root@office2a ~]$ service glusterd status glusterd dead but subsys locked [root@office2a ~]$ service glusterd restart Starting glusterd: [ OK ]
Same result on other host: [root@office4a ~]$ service glusterd stop [root@office4a ~]$ [ OK ] [root@office4a ~]$ service glusterd status glusterd dead but subsys locked [root@office4a ~]$ service glusterd start Starting glusterd: [ OK ] [root@office4a ~]$ service glusterd status glusterd (pid 23730) is running...
Reinstall: Did not finish, error messages as before. [root@office2a ~]$ service glusterd status glusterd dead but subsys locked [root@office2a ~]$ service glusterd stop [root@office2a ~]$ echo $? 0 [root@office2a ~]$ service glusterd status glusterd dead but subsys locked [root@office2a ~]$ Re-install now finished One thing I note: When gluster had been running (Comment 5) the "service glusterd stop" command produced an "[OK]" (on the following/wrong line). When glusterd was "dead", no "[OK]" was produced, although the exit code seems to be 0.
GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5. This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs". If there is no response by the end of the month, this bug will get automatically closed.
GlusterFS 3.4.x has reached end-of-life. If this bug still exists in a later release please reopen this and change the version or open a new bug.
GlusterFS 3.4.x has reached end-of-life.\ \ If this bug still exists in a later release please reopen this and change the version or open a new bug.