resourceSet issues - RAM not restricting

[irtaza9]

Are you using XOA or XO from the sources?

both

Which release channel?

both

Provide your commit number

6f578

Describe the bug

I created a resourceSet and set the maximum RAM to 4 GiB. Then, I created a VM within this resourceSet and checked the RAM from inside the VM console. It showed the same value as set in XO. However, when I increased the RAM from XO, exceeding the limit defined in the resourceSet, XO allowed me to do so. Upon checking the VM console again, it reflected the new RAM allocation. This leads me to believe that the resourceSet is not enforcing the defined limit.

Error message

resourceset is not restricting the RAM usage. VM created in a defined resourceset quota is over provisioning.

To reproduce

1. create a resourceset and add a user in it
2. login via that user
3. create a new vm on assigned resourceset
4. click the newly created vm and then change the RAM and apply
5. go in the console and check the RAM
6. the assigned RAM is apply on the VM

Expected behavior

As resourceSet is restricting defined Storage and CPU is should behave same for RAM too

Screenshots

Node

22

Hypervisor

XCP-ng 8.2.0

Additional context

I have already opened this issue on xcp-ng forum and here is the link to that.

[fordfusion240]

can confirm as well, that XOA doesnt instantly update the resource counters after RAM changes. But if you login as admin and goto Self service tab and click Recompute all limits, it will reflect your new RAM allocation for Resource set

[irtaza9]

We want that XO restrict user to the defined numbers for RAM as it is working fine with other params, i-e, Storage and CPU.