Bug 1319688 - Probing a new RHGS node, which is part of another cluster, should throw proper error message in logs and CLI
Summary: Probing a new RHGS node, which is part of another cluster, should throw prope...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: RHGS 3.1.3
Assignee: Satish Mohan
QA Contact: Byreddy
URL:
Whiteboard: glusterd
Depends On:
Blocks: 1311817
TreeView+ depends on / blocked
 
Reported: 2016-03-21 10:42 UTC by Gaurav Kumar Garg
Modified: 2016-09-17 16:47 UTC (History)
14 users (show)

Fixed In Version: glusterfs-3.7.9-1
Doc Type: Bug Fix
Doc Text:
When users attempted to add a node that was already part of another trusted storage pool to a new trusted storage pool with the 'gluster peer probe' command, the command failed, but did not give a clear reason for the failure. An error message has been added so that it is clear when the node is already part of another cluster.
Clone Of: 1237022
Environment:
Last Closed: 2016-06-23 05:04:52 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1240 0 normal SHIPPED_LIVE Red Hat Gluster Storage 3.1 Update 3 2016-06-23 08:51:28 UTC

Comment 3 Gaurav Kumar Garg 2016-03-21 10:46:26 UTC 
downstream patch for this bug: https://code.engineering.redhat.com/gerrit/70328
Comment 4 Gaurav Kumar Garg 2016-03-21 10:48:28 UTC 
this bug is to track the fix
which was already in 3.1.2 but missed out as part of rebasing to 3.1.3
from upstream 3.7.9
Comment 6 Byreddy 2016-04-04 07:31:41 UTC 
Verified this bug using the build "glusterfs-3.7.9-1"

Fix is working properly, The error message when tried to probe a node which is part of other cluster is proper with valid meaning.


Moving to verified state.
Comment 10 Atin Mukherjee 2016-06-14 03:33:01 UTC 
LGTM :)
Comment 12 errata-xmlrpc 2016-06-23 05:04:52 UTC 
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://access.redhat.com/errata/RHBA-2016:1240
Note You need to log in before you can comment on or make changes to this bug.