Description of problem: Glusterd is not started again automatically in an hyperconvergenced gluster setup after a graceful shutdown. Version-Release number of selected component (if applicable): ovirt-node-ng-installer-ovirt-4.2-2017122007 How reproducible: 100% Steps to Reproduce: 1. Install a three node hyperconvergenced gluster setup 2. Graceful shutdown of cluster (see additional info) 3. switch on all nodes Actual results: glusterd is not started by default Expected results: glusterd starts by default Additional info: Detailed Procedure to shutdown and start: https://lists.ovirt.org/pipermail/users/2018-January/086062.html. However the startup procedure is missing a "Disable global ha maintenance" before "7. Start VMs".
Tested with RHV 4.2.3 and gluster-3.12 When the node is gracefully shutdown, glusterd comes up automagically on the next boot
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.