Bug 1434921

Summary:	[Docs] [RHV] Host Disk I/O graph displayed data is not valid.
Product:	Red Hat CloudForms Management Engine	Reporter:	Ilanit Stein <istein>
Component:	Documentation	Assignee:	Red Hat CloudForms Documentation <cloudforms-docs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ilanit Stein <istein>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.7.0	CC:	adahms, dajohnso, hhudgeon, istein, jhardy, obarenbo
Target Milestone:	GA
Target Release:	cfme-future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	rhev:c&u:doc
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-09 00:02:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1424589
Bug Blocks:

Description Ilanit Stein 2017-03-22 15:24:33 UTC

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.2/html/managing_infrastructure_and_inventory/

Section Number and Name: 

Describe the issue: 
For RHV provider, in Host details page, under "Monitoring"->Utilization,
Disk I/O graph displays invalid data (always 0). 

** There is an RFE to make this graph contain valid data: bug 1424589.

Additional information: 
Note that for RHV __VMs__, the Disk IO graph data is valid.

Comment 2 Andrew Dahms 2017-05-04 23:12:13 UTC

Hi Ilanit,

Thank you for raising this bug.

I can see that some changes need to take place on the engineering side, but are there any specific changes you think we need to make in the docs?

Kind regards,

Andrew

Comment 3 Ilanit Stein 2017-05-05 06:07:35 UTC

The docs needs to be updated that the current data, displayed in __HOSTs__ Disk I/O graph is invalid (always 0).


(Once the RFE mentioned above will be implemented, this data will be valid)

Comment 4 Andrew Dahms 2017-05-05 06:19:01 UTC

Thanks, Ilanit - it sounds like we'll need to address this as a known issue for now, and remove the note after the RFE has been implemented.

Thanks for the clarification!

Comment 5 Andrew Dahms 2018-10-09 00:02:13 UTC

Closing out this bug in its role as a tracker of the release note ahead of the engineering fix in BZ#1424589.