Description of problem: Executing this: [root@s113 ~]# gluster volume add-brick gv0 replica 3 externalserver:/data/brick1/gv0 volume add-brick: failed: Pre Validation failed on externalserver. Please check log file for details. on an already working 2 server replica volume gv0, tells you to look inside the logfile: [2017-12-26 12:25:25.089637] I [MSGID: 106578] [glusterd-brick-ops.c:499:__glusterd_handle_add_brick] 0-management: replica-count is 3 [2017-12-26 12:25:25.089680] I [MSGID: 106481] [glusterd-brick-ops.c:312:gd_addbr_validate_replica_count] 0-management: Changing the replica count of volume gv0 from 2 to 3 [2017-12-26 12:25:25.138583] E [MSGID: 106116] [glusterd-mgmt.c:124:gd_mgmt_v3_collate_errors] 0-management: Pre Validation failed on externalserver. Please check log file for details. [2017-12-26 12:25:25.138664] E [MSGID: 106122] [glusterd-mgmt.c:1045:glusterd_mgmt_v3_pre_validate] 0-management: Pre Validation failed on peers [2017-12-26 12:25:25.138693] E [MSGID: 106122] [glusterd-mgmt.c:2136:glusterd_mgmt_v3_initiate_all_phases] 0-management: Pre Validation Failed [2017-12-26 12:27:41.620558] I [MSGID: 106487] [glusterd-handler.c:1475:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req (externalserver is just an alias for this bugreport / peer probe with the real name worked ) Which also says to look into the logfile (above). Would be nice if some"one" could add an error message, that tells the user, what in the Pre Validation check did not work :) Which btw, would interesst me very much atm... Version-Release number of selected component (if applicable): 3.10.8-1
the reference to "check log file" is ambiguous in this case, it was meant to say "check the log file of the failing node", because that gave out an error, which is not usefull ( again ), but at least gives a hint to the problem. In this case: [glusterd-utils.c:1166:glusterd_brickinfo_new_from_brick] 0-management: Failed to convert hostname externalserver to uuid No idea, how this can fail, but it did.
This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained. As a result this bug is being closed. If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately.