we have this issue [1], which is not reproducible in local environment
(after many tries and manipulations) it happens only once in awhile
is there any possibility to collect coredump after this occurs ?
however, if currently its a problem to leave vdsm that way (which i
think it is) until we figure that out, we'll post skiptest on that until
the libvirt_configure script will be converted to python code which will
be much easier to test and fix it
[1]
http://jenkins.ovirt.org/job/vdsm_master_unit_tests_gerrit/8135/console
--
Yaniv Bronhaim.