----- Original Message ----- > From: "Francesco Romani" <[email protected]> > To: "Sandro Bonazzola" <[email protected]> > Cc: [email protected], [email protected] > Sent: Tuesday, August 12, 2014 6:56:28 PM > Subject: Re: [ovirt-users] [QA] [ACTION REQUIRED] oVirt 3.5.0 RC2 status > > ----- Original Message ----- > > From: "Sandro Bonazzola" <[email protected]> > > To: [email protected], [email protected] > > Cc: "Doron Fediuck" <[email protected]>, "Eyal Edri" <[email protected]>, > > "Itamar Heim" <[email protected]>, "David > > Caro" <[email protected]>, "Yair Zaslavsky" <[email protected]>, > > [email protected], "Tal Nisan" > > <[email protected]>, "Mooli Tayer" <[email protected]>, "Francesco Romani" > > <[email protected]>, "Adam Litke" > > <[email protected]> > > Sent: Tuesday, August 12, 2014 5:43:40 PM > > Subject: [QA] [ACTION REQUIRED] oVirt 3.5.0 RC2 status > > > > Hi, > > tomorrow we should compose oVirt 3.5.0 RC2 starting at 08:00 UTC > > We still have the following blockers list: > > > > 1127460 virt NEW VM abnormal stop after > > extending when using thin > > provisioning on block storage > > [...] > > Analysis doesn't show yet a bug on VDSM, which seems to behave correctly > https://bugzilla.redhat.com/show_bug.cgi?id=1127460#c6 > https://bugzilla.redhat.com/show_bug.cgi?id=1127460#c7 > > NEEDINFO requests to QEMU and LVM maintainers are been sent, no answer yet. > > Since this was marked as blocker, I'll invest more time on this and will look > for a workaround, > if possible, within the end of the week.
This is very bad bug, but not a vdsm regression. It is broken in vdsm 3.4 and it will be still broken in vdsm 3.5, since getting fixes from qemu/kvm/lvm takes lot of time. Nir _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
