Hi Gianluca,

We are not using gluster, but FC storage.

All VM's from the pool are created from a template.

Regards,

Rik

On 5/16/19 6:48 PM, Gianluca Cecchi wrote:
> On Thu, May 16, 2019 at 6:32 PM Lucie Leistnerova <lleis...@redhat.com
> <mailto:lleis...@redhat.com>> wrote:
>
>     Hi Rik,
>
>     On 5/14/19 2:21 PM, Rik Theys wrote:
>>
>>     Hi,
>>
>>     It seems VM pools are completely broken since our upgrade to 4.3.
>>     Is anybody else also experiencing this issue?
>>
>     I've tried to reproduce this issue. And I can use pool VMs as
>     expected, no problem. I've tested clean install and also upgrade
>     from 4.2.8.7.
>     Version: ovirt-engine-4.3.3.7-0.1.el7.noarch with
>     ovirt-web-ui-1.5.2-1.el7ev.noarch
>>
>>     Only a single instance from a pool can be used. Afterwards the
>>     pool becomes unusable due to a lock not being released. Once
>>     ovirt-engine is restarted, another (single) VM from a pool can be
>>     used.
>>
>     What users are running the VMs? What are the permissions?
>     Each VM is running by other user? Were already some VMs running
>     before the upgrade?
>     Please provide exact steps.
>>
>>
> Hi, just an idea... could it be related in any way with disks always
> created as preallocated problems reported by users using gluster as
> backend storage?
> What kind of storage domains are you using Rik?
>
> Gianluca 

-- 
Rik Theys
System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10 bus 2440  - B-3001 Leuven-Heverlee
+32(0)16/32.11.07
----------------------------------------------------------------
<<Any errors in spelling, tact or fact are transmission errors>>

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7YU4VIWOFBN4MB4FDOHQCUIUSEHNW2TV/

Reply via email to