Description of problem: Global Utilization for CPU & Memory in Global Region is incorrect for Infrastructure Providers. The CPU & RAM data under "Global Utilization" pie chart simply become 2x for infrastructure providers in Global Region(both OSP & RHV) when a remote region subscription is added. Version-Release number of selected component (if applicable): cfme-5.10.12.3-20191029180220_f883bde How reproducible: Always Steps to Reproduce: 1. Add Infra provider A to Remote region 2. Add Infra provider B to Global region 3. Add Remote subscription to Global region Actual results: The Global utilization of provider B showing 2x values for CPU and Memory. Expected results: The Global utilization of provider B should show the actual values for CPU and Memory. Additional info: - In Global Region, the Summary View is showing the correct values. - In Global Region, the data under the "Cluster Utilization" for RHV and "Deployment Roles Utilization" in OSP Director providers remain correct with or without a remote subscription added.
New commit detected on ManageIQ/manageiq-ui-classic/ivanchuk: https://github.com/ManageIQ/manageiq-ui-classic/commit/e6aed35300b71c64b1d44c2ec0b9d091f60a8f60 commit e6aed35300b71c64b1d44c2ec0b9d091f60a8f60 Author: Milan Zázrivec <mzazrivec> AuthorDate: Wed Feb 19 09:52:53 2020 +0000 Commit: Milan Zázrivec <mzazrivec> CommitDate: Wed Feb 19 09:52:53 2020 +0000 Merge pull request #6544 from lpichler/remove_duplicates_in_infra_dasjboard Limit metric rollups to just default time profile (cherry picked from commit 56f20a0312713e82011d4cf26cf93d92a930377e) https://bugzilla.redhat.com/show_bug.cgi?id=1776684 app/services/ems_infra_dashboard_service.rb | 8 +- spec/services/ems_infra_dashboard_service_spec.rb | 28 + 2 files changed, 33 insertions(+), 3 deletions(-)
Verified on 5.11.5.1
Created attachment 1682999 [details] Screen shot of Provider global utilization before fix
Created attachment 1683000 [details] Screen shot of provider global utilization after fix
I've attached screen shots of provider global utilization before and after fix from the global appliance used to verify this BZ.
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-2020:2020