Describe the issue: 
===================
Came across this issue while verifying the doc bug[1]; on a 2X3 volume, failed to create snapshot if 1 brick of the volume is down.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1798861


Is this issue reproducible?
==========================
Always;
Was able to reproduce the issue on RHGS 3.5.3 build (6.0.45) and also on RHGS 3.3.0 build (3.8.4-44)


Steps to Reproduce:
==================
1. Create a X3 volume (1X3 or 2X3) and start it.
2. Kill one brick of the volume.
3. Create a snapshot of the volume using force option:
   # gluster snapshot create <snap-name> <vol-name> force


Actual results:
===============
Snapshot creation using 'force' even if one brick is down fails-

# gluster snapshot create snap2-post-killbrick vol1
snapshot create: failed: One or more bricks are not running. Please run volume status command to see brick status.
Please start the stopped brick and then issue snapshot create command or use [force] option in snapshot create to override this behavior.
Snapshot command failed

# gluster snapshot create snap2-post-killbrick vol1 force
snapshot create: failed: One or more bricks may be down.
Snapshot command failed


Expected results:
=================
As the RHGS Admin guide mentions-
""
Chpt : 8.2. Creating Snapshots
force - Snapshot creation will fail if any brick is down. In a n-way replicated Red Hat Gluster Storage volume where n >= 3 snapshot is allowed even if some of the bricks are down. In such case quorum is checked. Quorum is checked only when the force option is provided, else by-default the snapshot create will fail if any brick is down. Refer the Overview section for more details on quorum. 
""

Since the quorum was met in the above steps performed, snapshot creation should have been successful using force.