Il 12/01/2014 10:40, Maor Lipchuk ha scritto:
> Adding Sandro to the thread
>
> On 01/12/2014 11:26 AM, Maor Lipchuk wrote:
>> On 01/09/2014 12:29 PM, Nicolas Ecarnot wrote:
>>> Hi Maor, hi everyone,
>>>
>>> Le 07/01/2014 04:09, Maor Lipchuk a écrit :
>>>> Looking at bugzilla, it could be related to
>>>>
https://bugzilla.redhat.com/1029069
>>>> (based on the exception described at
>>>>
https://bugzilla.redhat.com/show_bug.cgi?id=1029069#c1)
>>>
>>> In my case, there where nothing "live" : the VM was shut down when
>>> creating the snapshot as well as when tyring to delete it.
>> I understand though live storage migration sub flows are, creation of
>> live snapshot, so it could be related.
>>>
>>>> The issue there was fixed after an upgrade to 3.3.1 (as Sander mentioned
>>>> it before in the mailing list)
>>>>
>>>> Could you give it a try and check if that works for you?
>>>
>>> I'm very shy with upgrading my oVirt production framework, but I began
>>> to read some things to upgrade it. Maybe you can lead me to a precise
>>> way to upgrade vdsm?
>> Sandro, do you aware of any documentation which can help in upgrading
>> ovirt, specifically VDSM?
No, I'm not aware of any documentation about it.
However since 3.3.1 is in ovirt-stable if you just need to update vdsm on a system I
think that
yum --enablerepo=ovirt-stable update "vdsm*"
on that system should be enough.
>>>> Also it will be great if you could open a bug on that
with the full
>>>> VDSM, engine logs and the list of lvs.
>>>
>>> Done :
>>>
>>>
https://bugzilla.redhat.com/show_bug.cgi?id=1050901
Just to close the bug :
I updated to 3.4.1-1.el6, and I can not reproduce the bug anymore.
--
Nicolas Ecarnot