[Bugs] [Bug 1406569] Element missing for arbiter bricks in XML volume status details output

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1406569

Ravishankar N <ravishankar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|arbiter                     |glusterd
           Assignee|ravishankar at redhat.com      |bugs at gluster.org



--- Comment #4 from Ravishankar N <ravishankar at redhat.com> ---
It is generally advisable to use separate paths for bricks but I don't think
symlink is the issue here. FWIW, I tried to create a similar setup like yours
and volume status printed everything:
-------------------------
0:root at vm1 bricks$ gluster v info
Volume Name: testvol
Type: Replicate
Volume ID: 822fdbac-6c7d-460c-8d89-3e6222c0ec11
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x (2 + 1) = 3
Transport-type: tcp
Bricks:
Brick1: 127.0.0.2:/bricks/disk0/brick1
Brick2: 127.0.0.2:/bricks/disk1/brick2
Brick3: 127.0.0.2:/bricks/disk2/brick3 (arbiter)


0:root at vm1 bricks$ ll /bricks/
total 0
drwxr-xr-x. 4 root root 33 Jan  6 11:26 disk0
drwxr-xr-x. 3 root root 20 Jan  6 11:26 disk1
lrwxrwxrwx. 1 root root 11 Jan  6 11:23 disk2 -> disk0/disk2

0:root at vm1 bricks$ tree /bricks/
/bricks/
├── disk0
│   ├── brick1
│   └── disk2
│       └── brick3
├── disk1
│   └── brick2
└── disk2 -> disk0/disk2

7 directories, 0 files

-------------------------

Changing the BZ component to glusterd for the glusterd folks to look at the
error message on comment #3.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.