Bug 1599823
| Summary: | [GSS] Error while creating new volume in CNS "Brick may be containing or be contained by an existing brick" | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Atin Mukherjee <amukherj> |
| Component: | glusterd | Assignee: | Sanju <srakonde> |
| Status: | CLOSED ERRATA | QA Contact: | Bala Konda Reddy M <bmekala> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | rhgs-3.3 | CC: | abhishku, akhakhar, amukherj, annair, atoborek, bkunal, bmekala, bturner, hchiramm, jarrpa, kaushal, madam, nchilaka, nravinas, pprakash, rhs-bugs, rreddy, rtalur, sankarshan, srakonde, srmukher, storage-qa-internal, tcarlin, vbellur, vdas, ykaul |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.12.2-14 | Doc Type: | Bug Fix |
| Doc Text: |
Earlier, during volume create, glusterd failed to handle blank real paths while checking if the brick path is already a part of another volume. Hence, volume create requests would fail.
This update fixes the path comparison logic. Now, glusterd can handle blank paths and prevents failure of volume create requests.
|
Story Points: | --- |
| Clone Of: | 1599803 | Environment: | |
| Last Closed: | 2018-09-04 06:50: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: | 1599783, 1599803 | ||
| Bug Blocks: | 1503138 | ||
|
Comment 13
Bala Konda Reddy M
2018-07-19 09:31:14 UTC
Updated the doc text. Kindly review an confirm (In reply to Srijita Mukherjee from comment #15) > Updated the doc text. Kindly review an confirm Looks good to me, I would like Atin to confirm it. Thanks, Sanju 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/RHSA-2018:2607 *** Bug 1685450 has been marked as a duplicate of this bug. *** |