Bug 1683467

Summary: No graph for memory utilization on the C & U utilization tab for the instances
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: UI - OPSAssignee: Robin Knaur <rknaur>
Status: CLOSED ERRATA QA Contact: Nandini Chandra <nachandr>
Severity: high Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: high    
Version: 5.9.4CC: bmidwood, dluong, dmetzger, hkataria, lavenel, lsmola, mpovolny, mshriver, nachandr, obarenbo, rchincho, rknaur, simaishi
Target Milestone: GAKeywords: ZStream
Target Release: 5.10.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.10.2.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1676761 Environment:
Last Closed: 2019-04-02 07:46:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Bug Depends On: 1676761    
Bug Blocks:    

Comment 2 CFME Bot 2019-03-06 18:07:44 UTC
New commit detected on ManageIQ/manageiq-providers-amazon/hammer:

https://github.com/ManageIQ/manageiq-providers-amazon/commit/5e74bc5f9b3bd2d501dd7f36c59da141a4b4b93a
commit 5e74bc5f9b3bd2d501dd7f36c59da141a4b4b93a
Author:     Ladislav Smola <lsmola>
AuthorDate: Tue Feb 26 08:15:17 2019 -0500
Commit:     Ladislav Smola <lsmola>
CommitDate: Tue Feb 26 08:15:17 2019 -0500

    Merge pull request #517 from PanSpagetka/memore-chart-available

    Return true for memory_mb_available?

    (cherry picked from commit 36109dfcda388e4347109ad01160c4a97135faff)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1683467

 app/models/manageiq/providers/amazon/cloud_manager/vm.rb | 4 +
 1 file changed, 4 insertions(+)

Comment 3 Nandini Chandra 2019-03-19 14:45:29 UTC
Verified in 5.10.2.0

Comment 5 errata-xmlrpc 2019-04-02 07:46:16 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/RHBA-2019:0694