Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1212576 - Inappropriate error message generated when non-resolvable hostname is given for peer in 'gluster volume create' command for distribute-replicate volume creation
Inappropriate error message generated when non-resolvable hostname is given f...
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd (Show other bugs)
3.0
All Linux
medium Severity medium
: ---
: RHGS 3.1.0
Assigned To: Gaurav Kumar Garg
SATHEESARAN
: Patch
Depends On: 1007209
Blocks: 1091935 1202842
  Show dependency treegraph
 
Reported: 2015-04-16 13:07 EDT by SATHEESARAN
Modified: 2016-06-05 19:38 EDT (History)
11 users (show)

See Also:
Fixed In Version: glusterfs-3.7.0-2.el6rhs
Doc Type: Bug Fix
Doc Text:
Previously for replicate volume the brick order check on volume create and add-brick was done by the cli. This check would fail when there is incorrect brick-order for replicate volume and it was showing ambiguous message "failed to resolve host name" even host name is correct. With this fix resolving hostname/ip-address will be done after brick have resolved by performing brick order check for replicate volume. consequence, the user will no longer be questioned and given an option to continue the operation when a bad brick order is given or the brick order check fails. In such a case, the user can use 'force' to bypass the check and allow the command to succeed.
Story Points: ---
Clone Of: 1007209
Environment:
Last Closed: 2015-07-29 00:40:59 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1495 normal SHIPPED_LIVE Important: Red Hat Gluster Storage 3.1 update 2015-07-29 04:26:26 EDT

  None (edit)
Comment 2 Atin Mukherjee 2015-04-16 13:17:09 EDT
The fix is already into upstream with http://review.gluster.org/9373
BZ should be moved to 'Modified' the moment branching takes place.
Comment 3 Gaurav Kumar Garg 2015-04-16 14:12:48 EDT
Another part of this bug fix also available in upstream master http://review.gluster.org/#/c/7589/
Comment 6 SATHEESARAN 2015-06-26 07:20:18 EDT
While creating a volume with the non-resolvable hostname , then proper error message is thrown as follows:

"volume create: test: failed: Host rhs-client345.lab.eng.blr.redhat.com is not in 'Peer in Cluster' state"

Tested with glusterfs-3.7.1-5.el6rhs

Marking this bug as VERIFIED
Comment 7 errata-xmlrpc 2015-07-29 00:40:59 EDT
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/RHSA-2015-1495.html

Note You need to log in before you can comment on or make changes to this bug.