memory quota calculation is broken

Bug #1044850 reported by Geoffrey Thomas on 2012-09-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Invirt Project
Undecided
Unassigned

Bug Description

It was reported in RT #2081303 that a user with a running 256-MB VM who is editing another 256-MB VM gets a form that claims he can increase the memory to 512 MB, but if he tries to do so, he gets a validation error claiming the maximum memory available to him is 256 MB (which is correct).

http://f.jwcxz.com/xvmwtf.png

I took a look at the code and don't see anything incredibly obvious -- it looks to me like both of those values are correctly calling the maxMemory function in invirt-web/code/validation.py. So I'm not sure what's going on.

Geoffrey Thomas (geofft) wrote :

Actually I'm not sure which is really correct -- in theory he could set the VM to 512 MB, if he's planning to turn off his other VM first.

So there's actually some UI work to be done here to explain the discrepancy. (That said, I don't think the two call sites _ought_ to have different opinions of what "max" means...)

no longer affects: xvm
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers