Description of problem:

When creating a thin-arbiter volume, if the replica-count provided is other than 2, the cli command fails(which is the expected behaviour) but it fails once transaction is committed on localhost.

This, ideally should be handled in cli itself.

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


How reproducible:
Try and create a volume with replica 3 and thin-arbiter 1 and provide 4 bricks in the cli.


Steps to Reproduce:
1. Run  gluster v create vol1 replica 3 thin-arbiter 1 node1:<brickpath> node2:<brickpath> node3:<brickpath> ta-node:<ta-path> force
2. 
3.

Actual results:
volume create: vol1: failed: Commit failed on localhost. Please check the log file for more details.


Expected results:
For thin-arbiter configuration, replica count must be 2 and thin-arbiter count must be 1. The 3rd brick of the replica will be the thin-arbiter brick



Additional info: