10 a.m.
Hi,
Yes, the user which tries to create a VM is a quota consumer, his quota
is defined on a datacenter. Storage quota for that perticular user is
set for 'all storage domains' (tried setting storage quota only on
storage domain, same result). We noticed that the bug only shows when we
create a VM from a template with thin provisioned disk. If template's
disk is preallocated, newly created disks are assigned ok (doesn't
matter if new VM's disk is preallocated or thin provisioned).
Let me know if you need more info.
JureKr
On 2.6.2013 14:37, Ofri Masad wrote:
Hi Jure,
The opened bug is not suppose to be in version 3.2.2
I've tried to reproduce the bug in 3.2.2 but could not reproduce it.
I would like to get to the bottom of this and in order to do so I'll need your help
with a detailed description of the bug.
few things I would like to make sure:
- The user which tries to create the VM from template is defined quota consumer for at
least one quota.
- The user quota include resource allocation to the storage domain which holds the VM
disk.
thanks in advance,
Ofri
----- Original Message -----
> From: "Doron Fediuck" <dfediuck(a)redhat.com>
> To: "Greg Padgett" <gpadgett(a)redhat.com>
> Cc: users(a)ovirt.org
> Sent: Thursday, May 30, 2013 9:31:50 AM
> Subject: Re: [Users] Disk quota and templates bug?
>
> ----- Original Message -----
>> From: "Greg Padgett" <gpadgett(a)redhat.com>
>> To: "Jure Kranjc" <jure.kranjc(a)arnes.si>
>> Cc: users(a)ovirt.org, "Doron Fediuck" <dfediuck(a)redhat.com>
>> Sent: Thursday, May 30, 2013 3:02:34 AM
>> Subject: Re: [Users] Disk quota and templates bug?
>>
>> On 05/29/2013 10:05 AM, Jure Kranjc wrote:
>>> Hi,
>>> we've encountered an quota allocation problem which seems like a bug.
>>> Using engine 3.2.2. on CentOS, datacenter in enforced quota mode.
>>> Scenario:
>>>
>>> - Create a virtual machine, seal it and create template from it. Assign
>>> some quota to it.
>>> - Create a new user, set new quota limits to his username
>>> - This user creates a new VM from this template. In new server/desktop
>>> dialog, resource allocation, new disk gets set to user's quota (user
only
>>> has permission for it's own quota). Create VM.
>>> - When VM is created it inherits the templates quota and not user's, as
>>> it
>>> should. So user is using templates disk quota. Quota for memory and vcpu
>>> works ok.
>>>
>>> No errors in engine.log.
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>> Hi Jure,
>>
>> Thanks for reporting this. I'm not well-versed enough with storage quotas
>> to assess, but adding Doron who should be able to help.
>>
>> Thanks,
>> Greg
>>
>>
> Hi Guys,
> This is indeed a bug which was reported a few weeks ago.
> It should be handled for 3.3.0.
> As a work around you should be able to modify the quota allocation
> after the VM is created.
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>