The current gluster volume info provides only server-ip:brick-path. This leads lot of confussion when a server has to many IPs (nic). It could be very much useful to resolve this, if the volume info command returns server uuid also along with other brick details like Brick<i>: <Server-UUID:Server-IP:Brick-Path> ex: Brick1: b2e7a030-2a72-4b14-a44a-87543f66e69e:192.168.122.87:/tmp/abc
REVIEW: http://review.gluster.org/4875 (Added server uuid into volume brick info) posted (#1) for review on master by Timothy Asir (tim.gluster)
REVIEW: http://review.gluster.org/4875 (cli: Add server uuid into volume brick info xml) posted (#2) for review on master by Timothy Asir (tim.gluster)
REVIEW: http://review.gluster.org/4875 (cli: Add server uuid into volume brick info xml) posted (#3) for review on master by Timothy Asir (tim.gluster)
REVIEW: http://review.gluster.org/4875 (cli: Add server uuid into volume brick info xml) posted (#4) for review on master by Timothy Asir (tim.gluster)
REVIEW: http://review.gluster.org/4875 (cli: Add server uuid into volume brick info xml) posted (#5) for review on master by Timothy Asir (tim.gluster)
REVIEW: http://review.gluster.org/4875 (cli: Add server uuid into volume brick info xml) posted (#6) for review on master by Timothy Asir (tim.gluster)
Assigning it to Timothy, since he is working on this bug.
COMMIT: http://review.gluster.org/4875 committed in master by Vijay Bellur (vbellur) ------ commit c12fccc4732df63273e8d013fd471e1c8f3b7d22 Author: Timothy Asir <tjeyasin> Date: Tue Apr 23 12:30:35 2013 +0530 cli: Add server uuid into volume brick info xml Add server uuid as an attribute to the existing brick details in the volume info cli xml output. Currently, when a node has more than one ip, the oVirt-engine fails to map the corresponding server using the ip alone. If we get the host uuid along with brick details in volume info command it will be easy for ovirt-engine to find out the server and thereby we can avoid confusion in finding the server. Change-Id: I3c9c9acea80e10e0b2977477759d9af045e48959 BUG: 955588 Signed-off-by: Timothy Asir <tjeyasin> Reviewed-on: http://review.gluster.org/4875 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.5.0, please reopen this bug report. glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user