Description of problem: I create a quota and enforce it on my DC. I add the user group under "Consumers". I can see the quota listed under my group. I cannot see the quota listed under a user in that group. When I try to create a VM as that user, it says it does not have access to that quota. CREATE_VM failed [Cannot add VM. The user is not a consumer of the Quota assigned to the resource.] Version-Release number of selected component (if applicable): RHV 4.3 Actual results: Only the group seems to take the quota but not the users Expected results: Group quotas are applied recursively to the users in that group
In the VM portal, there is no way to set which quota a VM should consume. The quota is copied from the VM template and the Blank template uses the Default quota.
Hello, I followed up with the customer and he confirmed the following: ~~~ I added "TestGroup" as a consumer of the default quota. It did let "testuser" create a VM when the quota is enforced. I still do not understand why when I assign "testuser" itself as a consumer of "TestQuota" that it behaves as expected and enforces that quota. Shouldn't it be broken in both cases if the VM creation is expecting to use the default quota? Does this mean we have to add each user individually to the quota for this to function? I'm not sure if multiple problems are at play here. ~~~
Any new updates or suggestions for the customer to try at this point?
It looks like a bug in a special case: When a user creates a VM from the 'Blank' template using the API (or VM portal), one of the user's quotas is assigned to the VM. The bug is that only quotas with the user assigned as consumer are considered, groups are ignored. Creating a VM from 'Blank' template is a special case. When creating a VM from any other template, the VM will have the same quota assigned as the template has. Another problem with this special case is if the user is a consumer of multiple quotas, then there is no way to specify which quota will be assigned to the VM.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Low: Red Hat Virtualization security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5179