The addmodule command reported an invalid password error if cluster on the new module is not running

Build tested: Github source for 1.1.1

/root/columnstore/mariadb-columnstore-server
commit f6cd94ea167789970db7b5b501569a6549495d10
Merge: 3d846d3 91b2553
Author: David.Hall <david.hall@mariadb.com>
Date: Tue Oct 24 09:15:58 2017 -0500

Merge pull request #72 from mariadb-corporation/MCOL-982

MCOL-982 Merge MariaDB 10.2.9

/root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine
commit af35345273b85b55f755303abc8cb0d1bea5fb89
Author: david hill <david.hill@mariadb.com>
Date: Thu Oct 26 17:38:25 2017 -0500

mcol-938 - fixed pm server ids

I have gluster installed on the new node but did not start it. Addmodule would report an invalid password error.

mcsadmin> addmodule pm 3 b1pm1,b1pm2,b1pm3 vagrant
addmodule Fri Oct 27 17:06:23 2017
gluster peer probe 10.0.0.101
ERROR: peer probe command failed.
FAILED: Invalid password
ERROR: No glusterd process detected at 10.0.0.101.
Start and enable glusterd and run postConfigure again.

Also, the error messages should not say "run postConfigure again"