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

bugzilla at redhat.com bugzilla at redhat.com
Tue Jan 10 21:36:16 UTC 2017


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



--- Comment #6 from Giuseppe Ragusa <giuseppe.ragusa at hotmail.com> ---
Hi,

I double checked and it seems that my history actually contains a gluster
command with the same exact syntax error ("details" vs "detail") that you
hinted to, maybe issued while investigating the problem: I mis-attributed the
error message to the correct command - I apologize for the confusion generated.

This time I checked better by issuing a:

date; gluster volume status home detail --xml; echo $? ; date

and actually the only log in that time interval is:

[2017-01-10 21:19:29.085296] I [MSGID: 106499]
[glusterd-handler.c:4331:__glusterd_handle_status_volume] 0-management:
Received status volume req for volume home

while the command still produces no device XML attribute for the arbiter brick
on the third distributed component of the replicated-distributed volume (and
the command still exits with status 0).

Now: what kind of tests/logs should I produce to fully trace the XML output
anomaly?

Please consider that this setup is in production phase now (so all tests must
not disrupt current activity, but maintenance windows can be arranged for).

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


More information about the Bugs mailing list