tree d33a2efa182869e6f24d74aa6427abfe1258befd
parent d7b5abc027d492a60ebf5059b27541fc04cfaab3
author Bankim Bhavsar <bankim@cloudera.com> 1614062606 -0800
committer Bankim Bhavsar <bankim@cloudera.com> 1614144827 +0000

[master] Fix validation for NON_VOTER on adding a master

When a master is added, validation check is made whether
the supplied master is already part of the Raft configuration.
However this check doesn't include NON_VOTER masters and hence
an InvalidArgument error is thrown later by the ChangeConfig
implementation in Raft. "master add" CLI is designed to specifically
catch Status::AlreadyPresent error to allow retries.

This change basically checks for all masters in the committed
Raft config irrespective of the member type on adding a master.

Change-Id: I10e6b3617b032c74ebed4359b10c36b7b365d9b7
Reviewed-on: http://gerrit.cloudera.org:8080/17108
Tested-by: Bankim Bhavsar <bankim@cloudera.com>
Reviewed-by: Alexey Serbin <aserbin@cloudera.com>