Bug 1599803

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:	Kaushal <kaushal>
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, bturner, hchiramm, jarrpa, kaushal, madam, nchilaka, pmulay, pprakash, rcyriac, rhinduja, rhs-bugs, rreddy, rtalur, sankarshan, srakonde, storage-qa-internal, vbellur, ykaul
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.3.1 Async
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:	1484412
Clones:	1599823 (view as bug list)		Environment:
Last Closed:	2018-07-19 06:00:10 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
Bug Blocks:	1484412, 1599823

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