[Bugs] [Bug 1377282] New: libgfapi-python functional test fails on CentOS CI against glusterfs nightly builds

[bugzilla at redhat.com]

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

            Bug ID: 1377282
           Summary: libgfapi-python functional test fails on CentOS CI
                    against glusterfs nightly builds
           Product: GlusterFS
           Version: mainline
         Component: libgfapi-python
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: ppai at redhat.com
                CC: bugs at gluster.org



Description of problem:
libgfapi-python functional test fails on CentOS CI against glusterfs nightly
builds. On one lucky day (16-Sep-2016) it passed.
https://ci.centos.org/view/Gluster/job/gluster_libgfapi-python/


Version-Release number of selected component (if applicable):
Glusterfs nightly builds


How reproducible:
Only on CentOS CI provisioned machines.
Not reproducible on my local centos7 VMs. 


Steps to Reproduce:
Run run-tests.sh script
https://github.com/gluster/glusterfs-patch-acceptance-tests/blob/master/centos-ci/libgfapi-python/run-test.sh


Actual results:
The tests exist abruptly with segmentation fault. This is almost consistently
encountered when running "test_mount_err" functional test. 


Expected results:
All functional tests should pass without any segmentation fault.


Additional info:
The test "test_mount_err" itself is pretty straightforward:
test/functional/libgfapi-python-tests.py

    def test_mount_err(self):
        # Volume does not exist
        fake_volname = str(uuid4().hex)[:10]
        vol = Volume(HOST, fake_volname)
        self.assertRaises(LibgfapiException, vol.mount)
        self.assertFalse(vol.mounted)

        # Invalid host - glfs_set_volfile_server will fail
        fake_hostname = str(uuid4().hex)[:10]
        vol = Volume(fake_hostname, VOLNAME)
        self.assertRaises(LibgfapiException, vol.mount)
        self.assertFalse(vol.mounted)

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