----- Original Message -----
> From: "Francesco Romani" <fromani(a)redhat.com>
> To: "Sandro Bonazzola" <sbonazzo(a)redhat.com>
> Cc: devel(a)ovirt.org, Users(a)ovirt.org
> 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" <sbonazzo(a)redhat.com>
>> To: Users(a)ovirt.org, devel(a)ovirt.org
>> Cc: "Doron Fediuck" <dfediuck(a)redhat.com>, "Eyal Edri"
<eedri(a)redhat.com>,
>> "Itamar Heim" <iheim(a)redhat.com>, "David
>> Caro" <dcaroest(a)redhat.com>, "Yair Zaslavsky"
<yzaslavs(a)redhat.com>,
>> ykaplan(a)redhat.com, "Tal Nisan"
>> <tnisan(a)redhat.com>, "Mooli Tayer" <mtayer(a)redhat.com>,
"Francesco Romani"
>> <fromani(a)redhat.com>, "Adam Litke"
>> <alitke(a)redhat.com>
>> 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.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at