Bug 1293792

Summary: [RFE][HC]Ensure quorum and no running tasks before moving host to maintenance
Product: [oVirt] ovirt-engine Reporter: Sahina Bose <sabose>
Component: BLL.GlusterAssignee: Ramesh N <rnachimu>
Status: CLOSED DUPLICATE QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: medium    
Version: futureCC: bmcclain, bugs, pcuzner, rcyriac
Target Milestone: ovirt-4.1.0-alphaKeywords: FutureFeature
Target Release: ---Flags: sabose: ovirt-4.1?
bmcclain: planning_ack+
sabose: devel_ack+
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-02 11:48:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1177771, 1277939    

Description Sahina Bose 2015-12-23 05:43:28 UTC
Description of problem:

When moving a host to maintenance in a hyper-converged cluster, check that quorum is available. If quorum is not met, and host is moved to maintenance - the gluster volume will become read-only and VMs paused.

Also, if rebalance, remov-brick or self-heal is running, host should not be moved to maintenance

Version-Release number of selected component (if applicable):
3.6

How reproducible:
NA

Additional info:
Users may need a way to override this warning and move host to maintenance.

Comment 1 Red Hat Bugzilla Rules Engine 2016-03-04 06:59:51 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Sandro Bonazzola 2016-05-02 09:49:17 UTC
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 3 Yaniv Lavi 2016-05-23 13:13:40 UTC
oVirt 4.0 beta has been released, moving to RC milestone.

Comment 4 Ramesh N 2016-11-02 11:48:25 UTC

*** This bug has been marked as a duplicate of bug 1213291 ***