Bug 1526118

Summary:	Stored C&U "CPU (Mhz)" values for RHV VMs are incorrect (too high) by a factor of two
Product:	Red Hat CloudForms Management Engine	Reporter:	Satoe Imaishi <simaishi>
Component:	C&U Capacity and Utilization	Assignee:	Boriso <bodnopoz>
Status:	CLOSED ERRATA	QA Contact:	Jan Zmeskal <jzmeskal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	5.8.0	CC:	bodnopoz, bsorota, istein, jhardy, jzmeskal, lsmola, obarenbo, sradco
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.9.0.13	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1495133	Environment:
Last Closed:	2018-03-01 13:22:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	RHEVM	Target Upstream Version:
Embargoed:
Bug Depends On:	1495133
Bug Blocks:

Comment 2 Jan Zmeskal 2017-12-15 16:16:17 UTC

Verified on:
CFME 5.0.9.13
RHV 4.1.7.6

Verification steps:
1. Have RHV provider with a running VM
2. SSH to the VM and create a load for resources mentioned in description for some minutes
3. In CFME UI, locate your machine and go to Monitoring -> Utilization
4. Choose interval to be Most Recent Hour
5. Now SSH to CFME appliance
6. Start rails console
7. Locate your VM (e.g. my_vm = cfme1 = Vm.all[2])
8. my_vm.perf_collect_metrics('realtime', 1.hour.ago)
9. Compare values returned by Utilization graphs and rails console

For me the values were the same in rails console and in UI. Of course they have been rounded in UI. For details see attached screenshots in attached archive cu.tar.gz

Comment 6 errata-xmlrpc 2018-03-01 13:22:12 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0380