Description of problem: Currently the gluster_base_class.py which containing the base class for all gluster cases, GlusterBaseClass in distaf.git. This should be moved to glusterfs.git where glusterfs related libraries and tests are located. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/14239 (distaf: Adding GlusterBaseClass to distaflibs-gluster) posted (#1) for review on master by M S Vishwanath Bhat (vbhat)
REVIEW: http://review.gluster.org/14239 (distaf: Adding GlusterBaseClass to distaflibs-gluster) posted (#2) for review on master by M S Vishwanath Bhat (vbhat)
REVIEW: http://review.gluster.org/14239 (distaf: Adding GlusterBaseClass to distaflibs-gluster) posted (#3) for review on master by M S Vishwanath Bhat (vbhat)
REVIEW: http://review.gluster.org/14239 (distaf: Adding GlusterBaseClass to distaflibs-gluster) posted (#4) for review on master by M S Vishwanath Bhat (vbhat)
COMMIT: http://review.gluster.org/14239 committed in master by M S Vishwanath Bhat (vbhat) ------ commit 6837b2793bc3d2cc488aa49491f3f5ff09e925b7 Author: M S Vishwanath Bhat <msvbhat> Date: Thu May 19 18:53:35 2016 +0530 distaf: Adding GlusterBaseClass to distaflibs-gluster GlusterBaseClass is the base class for gluster related test cases. This has setup() method which takes care of creating volumes with correct volume type after checking global_mode flags etc. So all tests are recommended to use this base class. The teardown() method is to teardown the setup that test has created. Each test case should teardown, any setup it does apart from what is done in setup(). The cleanup() method is used internally for cleaning up the volumes when there is a change of volume type between the tests. This patch also makes relevant import path changes. The changes from tc.nodes[] to tc.servers[] in distaf-core broke few tests. This patch fixes them. Change-Id: I1a8ae20ca7cac13b7d25c587f98c23b430054a57 BUG: 1333738 Signed-off-by: M S Vishwanath Bhat <msvbhat> Reviewed-on: http://review.gluster.org/14239 Tested-by: M S Vishwanath Bhat <vbhat> Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Apeksha D khakharia <akhakhar> Reviewed-by: Arthy Loganathan <aloganat> Reviewed-by: ShwethaHPanduranga
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.9.0, please open a new bug report. glusterfs-3.9.0 has been announced on the Gluster mailinglists [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://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/