Simulated the bug using gdb as below
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.
The new volume created successfully.
Hence marking this as verified
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.
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.