Bug 1422320

Summary: [Docs][RFE] A Gluster host will not move to maintenance if quorum is not met
Product: Red Hat Enterprise Virtualization Manager Reporter: Byron Gravenorst <bgraveno>
Component: DocumentationAssignee: rhev-docs <rhev-docs>
Status: CLOSED WONTFIX QA Contact: rhev-docs <rhev-docs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: gklein, lbopf, lsurette, rbalakri, srevivo, ykaul
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-18 06:56:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1213291    
Bug Blocks:    

Description Byron Gravenorst 2017-02-15 01:44:04 UTC 
Introduced a check in the host maintenance flow to ensure gluster quorum can me maintained for all gluster volumes which have the 'cluster.quorum-type' option set. Similarly there is a new check to ensure that the host moving to maintenance doesn't have a gluster brick which is a source of volume self-healing. These checks will be performed by default when moving the host to maintenance.

There is an option in the Manager to skip these checks, but this can result in bringing your system to halt. This option should be used in extreme cases.
Comment 1 Lucy Bopf 2017-04-18 06:56:06 UTC 
This behaviour is described in the Release Notes, and the checks and resulting messages are visible in the UI if the right conditions are met. No further procedural requirements appropriate for the RHV documentation were identified in the feature bug.

I am closing this bug.