On 24 Jul 2019, at 15:35, Benny Zlotnik <bzlotnik@redhat.com> wrote:
looks like https://bugzilla.redhat.com/show_bug.cgi?id=1665256 <https://bugzilla.redhat.com/show_bug.cgi?id=1665256> That’s not a very good resolution this bug was closed with. Are we ok with just accepting this behavior without any fix?? Not even just for OST sake, but rather the actual reliability of LSM
On Wed, Jul 24, 2019 at 3:55 PM Michal Skrivanek <michal.skrivanek@redhat.com <mailto:michal.skrivanek@redhat.com>> wrote: Hi, want to report a random failure I got in live_storage_migration test[1] as far as I can tell. I found stuck libvirt/qemu in vdsm logs[2], seemingly on storage access, no idea why. It passed afterwards in [3] with same binaries
Thanks, michal
[1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5159 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5159> [2] cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) in https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5159/artifact/export... <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5159/artifact/exported-artifacts/test_logs/basic-suite-master/post-004_basic_sanity.py/lago-basic-suite-master-host-1/_var_log/vdsm/vdsm.log> [3] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5162 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5162> _______________________________________________ Devel mailing list -- devel@ovirt.org <mailto:devel@ovirt.org> To unsubscribe send an email to devel-leave@ovirt.org <mailto:devel-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ <https://www.ovirt.org/site/privacy-policy/> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QSJZCCR7CF5MUV... <https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QSJZCCR7CF5MUV4LU6C53PAPMESBNG2Z/>