Bug #1402
Wrong parsing of float values from IM
Status: | Closed | Start date: | 08/04/2012 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | Ruben S. Montero | % Done: | 0% | |
Category: | Core & System | |||
Target version: | Release 3.8 | |||
Resolution: | fixed | Pull request: | ||
Affected Versions: | OpenNebula 3.6 |
Description
The OpenNebula core parse float values as 0 (as it is expecting a int value). The effect of this is that Monitoring data like
HYPERVISOR=kvm TOTALCPU=400 CPUSPEED=800 ... FREECPU=388.8 USEDCPU=11.199999999999989 ...
is parsed as:
HYPERVISOR=kvm TOTALCPU=400 CPUSPEED=800 ... FREECPU=0 USEDCPU=0
Associated revisions
bug #1402: Read monitor values as floats and truncate them to store in the host share
bug #1402: Always parse int values as floats and then truncate them
Revert "bug #1402: Always parse int values as floats and then truncate them"
breaks value tests, in quotas and VirtualMachine creation
This reverts commit 7dd75027e3f1722c138032b97ae949419e7fe217.
bug #1402: Always parse int values as floats and then truncate them
(cherry picked from commit 7dd75027e3f1722c138032b97ae949419e7fe217)
Revert "bug #1402: Always parse int values as floats and then truncate them"
breaks value tests, in quotas and VirtualMachine creation
This reverts commit 433f84e523e67919a7b3e2f8637bf9222f55b9d1.
Original commit is 7dd75027e3f1722c138032b97ae949419e7fe217.
Revert "bug #1402: Always parse int values as floats and then truncate them"
This reverts commit 7dd75027e3f1722c138032b97ae949419e7fe217.
History
#1 Updated by Ruben S. Montero almost 9 years ago
- Target version set to Release 3.8
#2 Updated by Ruben S. Montero almost 9 years ago
- Status changed from Assigned to Closed
- Resolution set to fixed