Bug 1237022
Summary: | Probing a new RHGS node, which is part of another cluster, should throw proper error message in logs and CLI | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> | |
Component: | glusterd | Assignee: | Gaurav Kumar Garg <ggarg> | |
Status: | CLOSED ERRATA | QA Contact: | Byreddy <bsrirama> | |
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rhgs-3.1 | CC: | amukherj, bmohanra, byarlaga, ggarg, mlawrenc, nlevinki, sankarshan, smohan, vbellur | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | RHGS 3.1.2 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | glusterd | |||
Fixed In Version: | glusterfs-3.7.5-0.3 | Doc Type: | Bug Fix | |
Doc Text: |
Previously, when the user tried to add a node to the existing cluster using "gluster peer probe \ <ip/hostname>" command, then the command failed without providing the proper cause of failure. With this fix, the proper error message is displayed during peer probe with an already existing cluster.
|
Story Points: | --- | |
Clone Of: | 1004699 | |||
: | 1252448 1319688 (view as bug list) | Environment: | ||
Last Closed: | 2016-03-01 05:27:18 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: | 1004699 | |||
Bug Blocks: | 1010153, 1216951, 1252448, 1260783 |
Description
SATHEESARAN
2015-06-30 08:37:59 UTC
I have noticed that there were messages neither in logs nor in CLI, about the actual reason of failure. User/Admin should be given few clues like - "host is already part of another cluster", which could be helpful and that is how RHGS used to fail in RHS 2.0 This is not a functional issue, but about requirement to provide helpful message in logs/CLI marking this bug as a known issue. Doc text is edited. Please sign off to be included in Known Issues. hi, this doc text looks good to me. Upstream patch merged: http://review.gluster.org/11884 With the RHGS version "glusterfs-3.7.5-0.3." This issue no more observed. Steps done: 1. Created two node (node-1 & node-2) cluster using rhel7.2 with rhgs 3.1.2 2. From another node (node-3) tried to peer probe the node-1 which is already part of cluster and got the error message saying that node (node-1) is already part of cluster. with above info, moving this bug to next state. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0193.html |