Description of problem: When peer probing an already probed server with the additional nic, the peer probe fails. Subsequent attempts to see the gluster peer status results in "gluster peer status failed messages. Version-Release number of selected component (if applicable): 3.7dev How reproducible: Steps to Reproduce: Gluster servers having 2 NICs each. 1 in the 10.x.x.x range and the other in the 192.x.x.x range servers were peer probed first with the 10.x.x.x addresses. server was then peer probed using the additional interface in the 192.x.x.x range Actual results: Failed to recognize the additional interface Expected results:
This is required for supporting multiple networks for gluster via oVirt
REVIEW: http://review.gluster.org/10122 (glusterd: Better GlusterD request validation) posted (#1) for review on master by Kaushal M (kaushal)
REVIEW: http://review.gluster.org/10122 (glusterd: Better GlusterD handshake request validation) posted (#2) for review on master by Kaushal M (kaushal)
REVIEW: http://review.gluster.org/10122 (glusterd: Better GlusterD handshake request validation) posted (#3) for review on master by Kaushal M (kaushal)
REVIEW: http://review.gluster.org/10122 (glusterd: Better GlusterD handshake request validation) posted (#4) for review on master by Kaushal M (kaushal)
COMMIT: http://review.gluster.org/10122 committed in master by Krishnan Parthasarathi (kparthas) ------ commit e0de0cd9b24169b90c95e1f6a87f05c060185089 Author: Kaushal M <kaushal> Date: Thu Apr 2 23:06:18 2015 +0530 glusterd: Better GlusterD handshake request validation To allow handshake requests to be validated correctly in a multi network environment, the request validation process has been improved. The handshake request initiator will add it's peer ID the request. The handshake request reciever will allow a request (as before) if, - it has no peers, or - the request came from a known peer Identifying the known peer is done as follows. - If the request contains a peer ID, it is matched against the IDs in the peer list. If a match is found, the request is allowed. - The address of the incoming request is matched against the peer addresses in the peer list. If a match is found, the request is allowed. - Otherwise, the request if disallowed Change-Id: I9eabe2935d16276bb147dfeebf8c8beb08e01411 BUG: 1207611 Signed-off-by: Kaushal M <kaushal> Reviewed-on: http://review.gluster.org/10122 Reviewed-by: Atin Mukherjee <amukherj> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user