*** This bug is a duplicate of bug 1514997 ***
https://bugs.launchpad.net/bugs/1514997
** This bug has been marked a duplicate of bug 1514997
Metrics filter receives wrong metric value
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1564182
Title:
CPU Metrics not working
Status in OpenStack Compute (nova):
In Progress
Bug description:
The metrics collection on compute nodes is currently not working.
When the compute node creates the object to save, it is divided to be
a value inside [0,1]. However, at the same time, when the scheduler
needs to pull out the numbers, it divides it once again as it pulls
the objects:
https://github.com/openstack/nova/blob/stable/liberty/nova/compute/resource_tracker.py#L437
https://github.com/openstack/nova/blob/stable/liberty/nova/compute/monitors/base.py#L60-L63
https://github.com/openstack/nova/blob/stable/liberty/nova/objects/monitor_metric.py#L68-L71
This essentially means that it always returns a value of zero as a
metric, because it divides a small number again by 100.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1564182/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
