Description of problem:
When the cluster.server-quorum-type option is set to 'none' on a volume, the cluster quorum status service for the volume needs to indicate that server quorum has been disabled for this volume.
When server quorum is enabled on a volume, the quorum status service indicates that quorum was regained for that volume. When server quorum is disabled on the same volume, the status information of the quorum status service remains the same, as follows -
QUORUM: Server quorum regained for volume vol2. Starting local bricks.
It should be updated with the information that server quorum is no longer enabled for this volume.
When none of the volumes in the cluster have quorum enabled, the quorum service is in pending state, suppose that server quorum is disabled on a volume, the service will continue to be in the pending state. It should be updated
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set cluster.server-quorum-type to server on a volume in the cluster being monitored by Nagios.
2. The quorum service shows that quorum was regained for that volume.
3. Set quorum type to none on the same volume.
The quorum service retains status information as "QUORUM: Server quorum regained for volume <vol-name>. Starting local bricks."
The quorum status service should indicate that server quorum was disabled on that volume.
Thank you for your report. However, this bug is being closed as it's logged against gluster-nagios monitoring for which no further new development is being undertaken.