oVirt List Archives
Sign In
Sign Up
Sign In
Sign Up
Manage this list
2024
December
November
October
September
August
July
June
May
April
March
February
January
2023
December
November
October
September
August
July
June
May
April
March
February
January
2022
December
November
October
September
August
July
June
May
April
March
February
January
2021
December
November
October
September
August
July
June
May
April
March
February
January
2020
December
November
October
September
August
July
June
May
April
March
February
January
2019
December
November
October
September
August
July
June
May
April
March
February
January
2018
December
November
October
September
August
July
June
May
April
March
February
January
2017
December
November
October
September
August
July
June
May
April
March
February
January
2016
December
November
October
September
August
July
June
May
April
March
February
January
2015
December
November
October
September
August
July
June
May
April
March
February
January
2014
December
November
October
September
August
July
June
May
April
March
February
January
2013
December
November
October
September
August
July
June
May
April
March
February
January
2012
December
November
October
September
August
July
June
May
April
March
February
January
2011
December
November
October
List overview
Download
thread
[ovirt-devel] Re: [OST] flaky storage test?
Michal Skrivanek
Friday, 26 July 2019
Fri, 26 Jul '19
8:45 a.m.
...
On 24 Jul 2019, at 15:35, Benny Zlotnik <bzlotnik(a)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(a)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/exp...
<
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5159/artifact/exp...
[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(a)ovirt.org <mailto:devel@ovirt.org> To unsubscribe send an email to devel-leave(a)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/QSJZCCR7CF5...
<
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QSJZCCR7CF5...
Attachments:
attachment.html
(text/html — 3.5 KB)
0
/
0
Reply
Back to the thread
Back to the list