Description of problem:
Please improve docs for: Assigning a Quota to an Object - Important box.
Something should be added to describe problem when Quota is enabled after there are some VMs and users defined.
Example:
When Quota is enabled and there exists a VM and the VM has assigned users with "administrative" (UserVmManager) roles, defining Quota on objects (VM, disk...) is not enough. The user has to be consumer of the quota too. This would be nice to clarify.
When the user is not consumer, this is in engine.log:
2013-01-25 14:12:04,320 WARN [org.ovirt.engine.core.bll.UpdateVmCommand] (ajp-/127.0.0.1:8702-7) [ffe16b] CanDoAction of action UpdateVm failed. Reasons:VAR__ACTION__UPDATE,VAR__TYPE__VM,USER_NOT_AUTHORIZED_TO_PERFORM_ACTION
Version-Release number of selected component (if applicable):
sf4
How reproducible:
100%
Steps to Reproduce:
1. Create a VM
2. Asign an user with UserVmManager role to the VM
3. Enable quota on DC
4. Try to change name/description of the VM in User Portal as the user above
Actual results:
Cannot change properties, as the user is not consumer of the quota.
Expected results:
Additional info:
After discussion I decided to change this BZ to real bug as I'm not sure if it is bug or not.
Description of problem:
An user with UserVmRole on a VM cannot modify VM's properties in User Portal, DC has Audit mode of quota, VM is in valid quota but the user itself is not consumer of the quota. Assigning the user to quota as consumer solves the issue, but quota mode is Audit... This is strange.
Error when editing VM's properties:
quotatest:
User is not authorized to perform this action.