Bug 1767656

Summary: [Regression] Unable to capture memory metric from Azure instances
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: C&U Capacity and UtilizationAssignee: Adam Grare <agrare>
Status: CLOSED ERRATA QA Contact: Nandini Chandra <nachandr>
Severity: high Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: medium    
Version: 5.10.6CC: dmetzger, obarenbo, rknaur, simaishi
Target Milestone: GAKeywords: Regression, ZStream
Target Release: 5.11.1Flags: pm-rhel: cfme-5.11.z+
simaishi: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.11.1.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1724415 Environment:
Last Closed: 2019-12-13 00:35:36 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: 1724415    
Bug Blocks:    

Comment 3 CFME Bot 2019-10-31 22:56:40 UTC 
New commit detected on ManageIQ/manageiq-providers-azure/ivanchuk:

https://github.com/ManageIQ/manageiq-providers-azure/commit/d0ba55867b3d6984575f69a5f18567975d0f49f9
commit d0ba55867b3d6984575f69a5f18567975d0f49f9
Author:     Adam Grare <agrare>
AuthorDate: Tue Sep 10 10:43:33 2019 -0400
Commit:     Adam Grare <agrare>
CommitDate: Tue Sep 10 10:43:33 2019 -0400

    Merge pull request #351 from AlexanderZagaynov/BZ-1724415_rename_memory_metric

    rename memory metric as it was before

    (cherry picked from commit b1e7848a74e496584bcf19ca278d1dcf8e611c24)

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

 app/models/manageiq/providers/azure/cloud_manager/metrics_capture.rb | 2 +-
 spec/models/manageiq/providers/azure/cloud_manager/metrics_capture_spec.rb | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
Comment 5 Nandini Chandra 2019-12-06 18:20:19 UTC 
Verified in 5.11.1.1
Comment 7 errata-xmlrpc 2019-12-13 00:35:36 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-2019:4201