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)
It's only the fake_volume bit that actually fails. If I comment that bit out, it passes correctly. It's worth checking if gluster fails with a fake volume. I've submitted a review request to skip this test so that the tests are green.
The builds are still failing for reasons other than what was originally reported here. The original issue was likely (as Niels had earlier pointed out) a side-effect of turning on io-threads in client by default. That was fixed in http://review.gluster.org/#/c/15620/ This BZ can be closed once the infra issue is addressed. Here's why the tests aren't being run now: 03:37:22 Cloning into 'libgfapi-python'... 03:42:22 fatal: unable to access 'https://review.gluster.org/libgfapi-python/': Operation timed out after 300021 milliseconds with 0 out of 0 bytes received 03:42:22 Build step 'Execute shell' marked build as failure 03:42:22 Performing Post build task...
Reported this as a bug in the CentOS CI infrastructure. Please follow https://bugs.centos.org/view.php?id=12662 for progress.