Red Hat Bugzilla – Bug 1289584
brick_up_status in tests/volume.rc is not correct
Last modified: 2016-06-16 09:49:19 EDT
Description of problem:
The brick_up_status function wasn't correct after the introduction of the RDMA port in to `volume status` output.
This caused regression tests using this function to fail in my salt-stack config based regression environment. This should have also caused the tests to fail in the current jenkins environment, but I'm not sure why it kept passing there.
REVIEW: http://review.gluster.org/12913 (tests: fix brick_up_status) posted (#1) for review on master by Kaushal M (email@example.com)
COMMIT: http://review.gluster.org/12913 committed in master by Kaleb KEITHLEY (firstname.lastname@example.org)
Author: Kaushal M <email@example.com>
Date: Tue Dec 8 19:06:24 2015 +0530
tests: fix brick_up_status
The brick_up_status function wasn't correct after the introduction of
the RDMA port into the `volume status` output.
It has been fixed to use the XML brick status of a specific brick
instead of normal CLI output.
Signed-off-by: Kaushal M <firstname.lastname@example.org>
Reviewed-by: Kaleb KEITHLEY <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
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.8.0, please open a new bug report.
glusterfs-3.8.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.