Bug #1363
Invalid Memory or Cpu values are not detected
| Status: | Closed | Start date: | 07/13/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | Release 3.8 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 3.6 |
Description
We should add sanity checks for attributes that are used for quotas or Host usage counters, like VM cpu and memory, or Image size.
Associated revisions
Bug #1363: Check correct value types for VM CPU, VCPU, MEM, and Image SIZE
bug #1363: Better check for int and float values
Bug #1363: Make VCPU optional again
Bug #1363: Check correct value types for VM CPU, VCPU, MEM, and Image SIZE
(cherry picked from commit c27c27ac4f197dfb2c81a90e918596713b19d728)
bug #1363: Better check for int and float values
(cherry picked from commit 057da9492bfc32e5a5ae9058261737cce5f5cfff)
Bug #1363: Make VCPU optional again
(cherry picked from commit fc08d847f2206f27aec59a847f5d437a566d2790)
History
#1
Updated by jordan pittier almost 9 years ago
I agree. Yesterday I got confused between CPU and vCPU and tried to put "0.1" as the value for vCPU in a template. I had to wait VM instantiation (which failed with a libvirt error) to see that I made a mistake.
#2
Updated by Ruben S. Montero almost 9 years ago
- Status changed from New to Closed
- Resolution set to fixed