|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
VirtualApplianceCommand#editVirtualAppliance
|
|
|
The physical resources consumed by the virtual machine when a node is deleted when the virtual app is running are not roll back.
How to detect it:
1. Create a virtual app, drag a virtual image
2. Power on the virtual app
3. Add another virtual image
4. Delete one virtual image
5. Check the phisical machine database and inspect the Xused resource tables
|
|
Description
|
The physical resources consumed by the virtual machine when a node is deleted when the virtual app is running are not roll back.
How to detect it:
1. Create a virtual app, drag a virtual image
2. Power on the virtual app
3. Add another virtual image
4. Delete one virtual image
5. Check the phisical machine database and inspect the Xused resource tables |
Show » |
|
Bug
Closed
Critical
The physical resources consumed by the virtual machine when a node is deleted when the virtual app is running are not roll back
I have a proposal (To improve it)
I think that for used resource we haven't to + or - the used resources.
Maybe is better to execute this query when we modify/create/delete a vm or vappliance (Check the disponibility)
select ram, cpu, hd from vm where hypervisor = x and state!= not deployed (Not deployed it's not necessary but is to assure)
Update physicalMachine set ramused = ram, cpuused=cpu, hdused = hd where hypervisor = x
We will assure to update correctly the value or solve a data inconsistency