Bug 1215018
| Summary: | [New] - gluster peer status goes to disconnected state. | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | RamaKasturi <knarra> |
| Component: | glusterd | Assignee: | Kaushal <kaushal> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.7.0 | CC: | bugs, dpati, gluster-bugs, jthottan, kaushal |
| Target Milestone: | --- | Keywords: | Reopened, TestBlocker, Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-16 12:54:19 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1186580, 1210301 | ||
|
Description
RamaKasturi
2015-04-24 06:54:27 UTC
when peer probing two systems which has two different nics, peer status always goes to disconnected state. Let us say i have nodes node1 and node2 having two ethernet cards eth0(10.70.36.x) and eth1 (10.70.33.x) When i try performing peer probe in the following way the node status always goes to disconnected state. From Node1: -------------- -------------- gluster peer probe eth0(node2) gluster peer probe eth1(node2) From Node2: ------------- ------------- gluster peer probe eth1(node1) With out this feature RHSC QE team is blocked on testing gluster network feature. REVIEW: http://review.gluster.org/10495 (glusterd: Stricter matching for peerinfo in glusterd_peer_rpc_notify) posted (#1) for review on master by Kaushal M (kaushal) COMMIT: http://review.gluster.org/10495 committed in master by Kaushal M (kaushal) ------ commit 02583099a219ce327aac62af22b486c7b9fcb531 Author: Kaushal M <kaushal> Date: Wed May 6 13:10:15 2015 +0530 glusterd: Use generation number to find peerinfo in RPC notifications The generation number for each peerinfo object is unique. It can be used to find the exact peerinfo object, which is required for peer RPC notifications. Using hostname and uuid matching to find peerinfos can return incorrect peerinfos to be returned in certain cases like multi network peer probe. This could cause updates to happen to incorrect peerinfos. Change-Id: Ia0aada8214fd6d43381e5afd282e08d53a277251 BUG: 1215018 Signed-off-by: Kaushal M <kaushal> Reviewed-on: http://review.gluster.org/10495 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System Reviewed-by: Atin Mukherjee <amukherj> RDMA feature testing from console point of view is failing and it's failing even without console. So, it's marked as a blocker. REVIEW: http://review.gluster.org/10623 (glusterd: Use generation number to find peerinfo in RPC notifications) posted (#1) for review on release-3.7 by Kaushal M (kaushal) 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 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 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 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 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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |