Description of problem: The Gluster Test Framework has no initial sanity checks in place at the moment, to ensure known dependencies are in place before running the full test suite. (eg dbench, git, mock, nfs-utils, xfsprogs, etc) If a developer runs the Gluster Test Framework without some of these known dependencies, the failures may only show up 1/2 hour later (or more) instead of right away. Since it's very simple to add some initial sanity checks to the test scripting, we should do so. Version-Release number of selected component (if applicable): Upstream Gluster git, master branch as of Wed 5th March 2014. How reproducible: Every time.
REVIEW: http://review.gluster.org/7193 (tests: Add initial sanity checks to the GlusterFS Test Framework) posted (#1) for review on master by Justin Clift (justin)
REVIEW: http://review.gluster.org/7193 (tests: Add initial sanity checks to the GlusterFS Test Framework) posted (#2) for review on master by Justin Clift (justin)
REVIEW: http://review.gluster.org/7193 (tests: Add initial sanity checks to the GlusterFS Test Framework) posted (#3) for review on master by Justin Clift (justin)
REVIEW: http://review.gluster.org/7193 (tests: Add initial sanity checks to the GlusterFS Test Framework) posted (#4) for review on master by Justin Clift (justin)
COMMIT: http://review.gluster.org/7193 committed in master by Vijay Bellur (vbellur) ------ commit bed3fcd3a47d3ca35b3536e0cad2b293dd240ce4 Author: Justin Clift <justin> Date: Thu Mar 6 16:53:50 2014 +0000 tests: Add initial sanity checks to the GlusterFS Test Framework BUG: 1073168 Change-Id: I0b995d94fe83053d3294df1b5fad2eef3b4355d3 Signed-off-by: Justin Clift <justin> Reviewed-on: http://review.gluster.org/7193 Reviewed-by: Niels de Vos <ndevos> Tested-by: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/8600 (tests: Don't check for init process.) posted (#1) for review on master by Raghavendra Talur (rtalur)
COMMIT: http://review.gluster.org/8600 committed in master by Vijay Bellur (vbellur) ------ commit 165cf459cf2a61c391d16928d58b34543a7ec94e Author: Raghavendra Talur <rtalur> Date: Thu Sep 4 19:30:48 2014 +0530 tests: Don't check for init process. As a way of checking for existence of pidof we were checking for init process, which may not be true in case of Containers. Change-Id: I402e7ab4f2459057826ed24094e87dd605eaac8a BUG: 1073168 Signed-off-by: Raghavendra Talur <rtalur> Reviewed-on: http://review.gluster.org/8600 Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Jeff Darcy <jdarcy> Reviewed-by: Vijay Bellur <vbellur> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Harshavardhana <harsha> Tested-by: Harshavardhana <harsha>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
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.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users