Bug 1599803 - [GSS] Error while creating new volume in CNS "Brick may be containing or be contained by an existing brick"
Summary: [GSS] Error while creating new volume in CNS "Brick may be containing or be c...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: RHGS 3.3.1 Async
Assignee: Kaushal
QA Contact: Bala Konda Reddy M
URL:
Whiteboard:
Depends On: 1599783
Blocks: 1484412 1599823
TreeView+ depends on / blocked
 
Reported: 2018-07-10 15:46 UTC by Atin Mukherjee
Modified: 2020-12-14 11:05 UTC (History)
24 users (show)

Fixed In Version: glusterfs-3.8.4-54.15
Doc Type: Bug Fix
Doc Text:
Previously, glusterd could not handle blank real paths when checking if brick path is already a part of another volume, during volume create. Hence, volume create requests would fail with the error 'Brick may be containing or be contained by an existing brick'. This update fixes the path comparison logic to correctly handle blank paths, and thus prevents failure of further volume create requests.
Clone Of: 1484412
: 1599823 (view as bug list)
Environment:
Last Closed: 2018-07-19 06:00:10 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2222 0 None None None 2018-07-19 06:00:49 UTC

Comment 8 Bala Konda Reddy M 2018-07-13 14:21:54 UTC 
Build: 3.8.4-54.15

On a live-build(3.8.4-54.10) I hit the issue by following the below steps.

1. Ran glusterd with gdb prior to that install glusterfs-debuginfo packages
   gdb -p `pidof glusterd`
2. Do "b glusterd_is_brickpath_available" and continue using c
3. Go till line 1326 (where brickinfo->real_path will get the brick path for creating the volume)
4. perform  p brickinfo->real_path = "" and continued the steps  
5. The volume will fail.

Now with the fix, followed the above steps
The new volume created successfully.

Hence marking this as verified
Comment 19 errata-xmlrpc 2018-07-19 06:00:10 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-2018:2222
Note You need to log in before you can comment on or make changes to this bug.