[Bugs] [Bug 1051992] Peer stuck on "accepted peer request"

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1051992

Joonas Vilenius <rhbugzilla at ajaton.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rhbugzilla at ajaton.net



--- Comment #2 from Joonas Vilenius <rhbugzilla at ajaton.net> ---
Possibly related so i'll provide my story` but if needed i'll either submit a
new bug or move the comment to some more appropriate existing bug.

Since we upgraded to 3.4.5 we haven't added any peers to the existing cluster.
Now as it is attempted it seems to always fail.

Some details for starters:
- Debian Wheezy (amd64)
- 12 existing servers in the cluster
- 4 new servers in another datacenter
- network expanded between the datacenters
- GlusterFS 3.4.5-1 from Debian packages

1. gluster peer status reports 11 peers, all in state Peer in Cluster
(Connected)
2. host gluster13 is empty, glusterfs installed and started, minimal amount of
data under /var/lib/glusterd
3. gluster peer probe gluster13 from gluster01 reports "peer probe: success"
4. gluster peer status run on gluster01 reports now for the added host:

Hostname: gluster13
Port: 24007
Uuid: 2902f0a9-73ba-48ea-a185-e2a94799ac3b
State: Peer Rejected (Connected)

5. gluster peer status run on gluster13 reports:

Hostname: 10.10.30.101
Port: 24007
Uuid: 0a684cf6-ae7c-44a5-b7a4-16173f311e45
State: Peer Rejected (Connected)

6. /var/lib/glusterd/peers/0a684cf6-ae7c-44a5-b7a4-16173f311e45 contains:

uuid=0a684cf6-ae7c-44a5-b7a4-16173f311e45
state=6
hostname1=10.10.30.101

7. on gluster13 the /var/log/glusterfs/etc-glusterfs-glusterd.vol.log contains:

[2014-12-30 12:26:19.748973] I [glusterd-rpc-ops.c:225:__glusterd_probe_cbk]
0-glusterd: Received probe resp from uuid:
0a684cf6-ae7c-44a5-b7a4-16173f311e45, host: 10.10.30.101
[2014-12-30 12:26:19.807746] I [glusterd-rpc-ops.c:295:__glusterd_probe_cbk]
0-glusterd: Received resp to probe req
[2014-12-30 12:26:19.807838] I
[glusterd-rpc-ops.c:345:__glusterd_friend_add_cbk] 0-glusterd: Received RJT
from uuid: 0a684cf6-ae7c-44a5-b7a4-16173f311e45, host: 10.10.30.101, port: 0

At this point i get puzzled.. I'm not doing anything differently than with the
existing 12 hosts.. No firewall in between, same network, ..

I can see all the existing volumes and some details of them from the gluster13
even while i'm rejected from the trusted peers but i cannot create for example
a new volume to the new hosts.

If i probe from gluster13 to gluster15 (13-16 are the new hosts) they get
peered without issues!?

As said, i'm puzzled, where does the reject come from?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.