It might be worth if you can open a github issue https://github.com/gluster/glusterd2/issues with all the details so that this doesn't go out of from our radar.
On Thu, Jun 14, 2018 at 10:25 PM, Davide Obbi <davide.o...@booking.com> wrote: > thanks, > > i have been able to remove the old id entry: > 5953d666-fccd-48e2-aeb9-5308a53ad5a0 > succesfully > > On Thu, Jun 14, 2018 at 4:07 PM, Aravinda <avish...@redhat.com> wrote: > >> Hi, >> >> Thanks for the feedback, I will look into the issue. >> >> Gluster 4.1 version, glustercli allows to detach peer using peer id as >> well. As a workaround can you try using REST API as below >> >> curl -i -XDELETE http://localhost:24007/v1/peers/<peerid> >> >> For example, curl -i -XDELETE http://localhost:24007/v1/peer >> s/00590d47-950d-4047-82d5-60f941c51827 >> >> Peer id as shown in `glustercli peer status` >> >> >> On 06/13/2018 05:16 AM, Davide Obbi wrote: >> >> hi, >> >> i'm testing some operations with gluster4 and glustercli. >> I have re-installed a node with the same host name/IP and add it back to >> the cluster. >> This resulted in a double entry, this could be expected but then i am not >> able to remove the old one nor the new nor any other node. >> So at this point i am not sure i run peer detach correctly or something >> is not working as expected or everything broke by re-adding the same node >> again since i get always: >> >> Error: Unable to find Peer ID >> >> thanks >> Davide >> >> >> Usage: >> glustercli peer detach <HOSTNAME> [flags] >> >> +--------------------------------------+-------------------- >> --------------------+---------------------+ >> >> | ID | >> NAME | PEERADDRESSES | >> >> +--------------------------------------+-------------------- >> --------------------+---------------------+ >> >> | 00590d47-950d-4047-82d5-60f941c51827 | glusternode-2405 | >> 10.10.10.1:24008 | >> >> | 5953d666-fccd-48e2-aeb9-5308a53ad5a0 | glusternode-2401 | >> 10.10.10.2.15:24008 | >> >> | 79ffdcbf-5147-4f7e-b28d-1fa056cd3ccc | glusternode-2404 | >> 10.10.10.3:24008 | >> >> | ba9e411e-9b69-4841-8b36-e1dbb5663135 | glusternode-2401 | >> 10.10.10.2:24008 | >> >> +--------------------------------------+-------------------- >> --------------------+---------------------+ >> >> [root@glusternode-2404 ~]# glustercli peer detach >> 00590d47-950d-4047-82d5-60f941c51827 >> Peer detach failed >> >> Error: Unable to find Peer ID >> [root@glusternode-2404 ~]# glustercli peer detach >> 5953d666-fccd-48e2-aeb9-5308a53ad5a0 >> Peer detach failed >> >> Error: Unable to find Peer ID >> [root@glusternode-2404 ~]# glustercli peer detach glusternode-2401 >> Peer detach failed >> >> Error: Unable to find Peer ID >> [root@glusternode-2404 ~]# glustercli peer detach glusternode-2404 >> Peer detach failed >> >> Error: Unable to find Peer ID >> >> >> >> >> >> _______________________________________________ >> Gluster-users mailing >> listGluster-users@gluster.orghttp://lists.gluster.org/mailman/listinfo/gluster-users >> >> >> >> -- >> regards >> Aravinda VK >> >> > > > -- > Davide Obbi > System Administrator > > Booking.com B.V. > Vijzelstraat 66-80 Amsterdam 1017HL Netherlands > Direct +31207031558 > [image: Booking.com] <https://www.booking.com/> > The world's #1 accommodation site > 43 languages, 198+ offices worldwide, 120,000+ global destinations, > 1,550,000+ room nights booked every day > No booking fees, best price always guaranteed > Subsidiary of Booking Holdings Inc. (NASDAQ: BKNG) > > _______________________________________________ > Gluster-users mailing list > Gluster-users@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users >
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users