[MCOL-989] The addmodule command reported an invalid password error if cluster on the new module is not running Created: 2017-10-27  Updated: 2023-10-26  Resolved: 2017-11-09

Status: Closed
Project: MariaDB ColumnStore
Component/s: ?
Affects Version/s: 1.1.1
Fix Version/s: 1.1.2

Type: Bug Priority: Major
Reporter: Daniel Lee (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Sprint: 2017-22

 Description   

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"

 Comments   
Comment by Ben Thompson (Inactive) [ 2017-11-08 ]

To trigger this message attempt mcsadmin addmodule command with a password provided (non-ssh) and have the new module NOT running the glusterd service.

Comment by Ben Thompson (Inactive) [ 2017-11-08 ]

Fix command string missing space and error messages to not reference postConfigure since this can happen under addmodule mcsadmin command.

Comment by Daniel Lee (Inactive) [ 2017-11-09 ]

Build verified: 1.1.2 Github source

/root/columnstore/mariadb-columnstore-server
commit ed21e674cfd70db421957d0212ff7fc1835d06d5
Author: david hill <david.hill@mariadb.com>
Date: Mon Nov 6 08:41:53 2017 -0600

Update README.md

updated version

/root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine
commit e0febdcd1a88bc3fab55519bd679f93719687ccc
Merge: 1603ce9 f1dd92a
Author: david hill <david.hill@mariadb.com>
Date: Wed Nov 8 15:32:50 2017 -0600

Merge pull request #313 from mariadb-corporation/MCOL-989

MCOL-989

mcsadmin> addmodule pm 2 s3pm1,s3pm2 vagrant
addmodule Thu Nov 9 18:02:11 2017
gluster peer probe 10.0.0.81
ERROR: peer probe command failed.
ERROR: No glusterd process detected at 10.0.0.81.
Start and enable glusterd at 10.0.0.81.
mcsadmin> addmodule pm 2 s3pm1,s3pm2 vagrant
addmodule Thu Nov 9 18:03:02 2017
gluster peer probe 10.0.0.81
gluster peer probe 10.0.0.82

Data Redundancy storage will be expanded when module(s) are added.

Number of DBRoots Per Performance Module you want to add
Please enter: 2

Adding Modules pm3, pm4, please wait...
Add Module(s) successfully completed

Enabling Modules
Successful Enable of Modules

Adding DBRoots
New DBRoot IDs added = 3, 4, 5, 6

Assigning DBRoots

DBRoot IDs assigned to 'pm3' =

Changes being applied

DBRoot IDs assigned to 'pm3' = 3, 4

Successfully Assigned DBRoots
DBRoot IDs assigned to 'pm4' =

Changes being applied

DBRoot IDs assigned to 'pm4' = 5, 6

Successfully Assigned DBRoots

Run Data Redundancy Setup for DBRoots
gluster peer probe 10.0.0.81
gluster peer probe 10.0.0.82
Gluster create and start volume dbroot3...DONE
Gluster create and start volume dbroot4...DONE
Gluster create and start volume dbroot5...DONE
Gluster create and start volume dbroot6...DONE

Successfully Completed Data Redundancy Add DBRoots

addModule Command Successfully completed: Run startSystem command to Activate newly added Performance Modules

Generated at Thu Feb 08 02:25:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.