Bug 1213245
| Summary: | Volume creation fails with error "host is not in 'Peer in Cluster' state" | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Anand Nekkunti <anekkunt> |
| Component: | glusterd | Assignee: | Anand Nekkunti <anekkunt> |
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | rhgs-3.0 | CC: | amukherj, anekkunt, annair, asrivast, bmohanra, lmohanty, mmccune, mzywusko, nlevinki, nsathyan, sabose, sasundar, vagarwal, vbellur |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | glusterd | ||
| Fixed In Version: | glusterfs-3.7.0-2.el6rhs | Doc Type: | Bug Fix |
| Doc Text: |
Previously, if peer probe is executed using IPs then volume creation was also done using IPs. With this release peer probe can be done using IP's and volume creation can be done using host name and vice-versa.
|
Story Points: | --- |
| Clone Of: | 1055928 | Environment: | |
| Last Closed: | 2015-07-29 04:41:20 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: | 1055928 | ||
| Bug Blocks: | 1202842 | ||
|
Comment 1
Vivek Agarwal
2015-04-20 08:13:03 UTC
Tested with RHGS 3.1 Nightly Build ( glusterfs-3.7.1-2.el6rhs ) with the following test case : 1. Created a 'Trusted Storage Pool' using network shortnames 2. Created a distributed-replicate volume using IP's of the hosts. There were no issues in this case Marking this bug as VERIFIED Hi Anand, The doc text is updated. Please review the same and share your technical review comments. If it looks ok, then sign-off on the same. Regards, Bhavana Hi Bhavana Doc text looks good to me . 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 |