Bug 1879517

Summary: Object Service Dashboard should use RGW pool prefix in queries for RGW metrics in case of external mode
Product: OpenShift Container Platform Reporter: Anmol Sachan <asachan>
Component: Console Storage PluginAssignee: Bipul Adhikari <badhikar>
Status: CLOSED ERRATA QA Contact: Rachael <rgeorge>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.6CC: aos-bugs, ebenahar, nberry, nthomas
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:41:19 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:

Description Anmol Sachan 2020-09-16 12:52:24 UTC
Description of problem: Currently the RGW capacity usage and data resiliency queries are same for both internal and external mode. The queries should use the RGW pool prefix supplied with external cluster secret in case of external mode. 


Version-Release number of selected component (if applicable):


How reproducible: 100 %


Steps to Reproduce:
1.Create an internal mode OCS cluster and deploy object storage workload on it. Workload should be of both MCG and RGW.
2.Create an external mode cluster and deploy object storage workload on it. Workload should be of both MCG and RGW.

Actual results: In case of external mode RGW pool prefix is not considered and gives no result in metrics.


Expected results: In case of external mode RGW pool prefix should be considered.


Additional info:

Comment 5 errata-xmlrpc 2020-10-27 16:41:19 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 (OpenShift Container Platform 4.6 GA Images), 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:4196