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.
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.