On 13 June 2017 at 11:15, Atin Mukherjee <amukherj@xxxxxxxxxx> wrote:
This looks like a bug in the error code as the error message is wrong. I'll take a look at it and get back.
I had a thought (they do happen) and tried some further testing.
root@gh1:~# gluster peer status
Number of Peers: 2
Hostname: gh2.brian.softlog
Uuid: b59c32a5-eb10-4630-b147-890a98d0e51d
State: Peer in Cluster (Connected)
Hostname: gh3.brian.softlog
Uuid: 825afc5c-ead6-4c83-97a0-fbc9d8e19e62
State: Peer in Cluster (Disconnected)
root@gh1:~# gluster peer detach gh3
peer detach: failed: gh3 is not part of cluster
root@gh1:~# gluster peer detach gh3.brian.softlog
peer detach: success
Number of Peers: 2
Hostname: gh2.brian.softlog
Uuid: b59c32a5-eb10-4630-b147-890a98d0e51d
State: Peer in Cluster (Connected)
Hostname: gh3.brian.softlog
Uuid: 825afc5c-ead6-4c83-97a0-fbc9d8e19e62
State: Peer in Cluster (Disconnected)
root@gh1:~# gluster peer detach gh3
peer detach: failed: gh3 is not part of cluster
root@gh1:~# gluster peer detach gh3.brian.softlog
peer detach: success
Specifying the FQDN of the peer seems to do the trick, with no need for force either.
nb: Just using the host name while the host is up does work.
--
Lindsay
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
