Bug 1883810 - [External mode] RGW metrics is not available after OCS upgrade from 4.5 to 4.6
Summary: [External mode] RGW metrics is not available after OCS upgrade from 4.5 to 4.6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: rook
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: OCS 4.6.0
Assignee: Anmol Sachan
QA Contact: Rachael
URL:
Whiteboard:
Depends On: 1888134
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-30 09:52 UTC by Rachael
Modified: 2023-09-15 00:48 UTC (History)
9 users (show)

Fixed In Version: 4.6.0-137.ci
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1888134 (view as bug list)
Environment:
Last Closed: 2020-12-17 06:24:38 UTC
Embargoed:


Attachments (Terms of Use)
Object Service dashboard post upgrade (60.77 KB, image/png)
2020-09-30 09:52 UTC, Rachael
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift rook pull 134 0 None closed Bug 1881071: ceph: adding '--upgrade' option to the script 2020-12-28 06:47:03 UTC
Github rook rook pull 6392 0 None closed ceph: adding '--upgrade' option to external script 2020-12-28 06:47:03 UTC
Red Hat Product Errata RHSA-2020:5605 0 None None None 2020-12-17 06:24:54 UTC

Description Rachael 2020-09-30 09:52:35 UTC
Created attachment 1717801 [details]
Object Service dashboard post upgrade

Description of problem (please be detailed as possible and provide log
snippets):

After upgrading the external mode cluster from OCS 4.5 to 4.6, the metrics for RGW is not available under the Object Service dashboard.

Version of all relevant components (if applicable):
ocs-operator.v4.6.0-573.ci
OCP: 4.6.0-0.ci-2020-09-30-031307

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, metrics are not available for RGW

Is there any workaround available to the best of your knowledge?
Not that I am aware of

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
Yes

If this is a regression, please provide more details to justify this:
No

Steps to Reproduce:
1. Upgrade OCS 4.5 to OCS 4.6 in external mode
2. Check Object Service dashboard


Actual results:
The RGW metrics although listed in the dropdown, are not available

Expected results:
The metrics should be available after upgrade to 4.6

Comment 2 Elad 2020-10-07 09:46:45 UTC
RGW metrics is a 4.6 feature and this bug is a blocker for it. Therefore, proposing as a blocker

Comment 7 Michael Adam 2020-10-13 08:21:06 UTC
backport in rook 1.4 is merged: https://github.com/rook/rook/pull/6423

Comment 8 Michael Adam 2020-10-13 08:23:43 UTC
backport PR to release-4.6: https://github.com/openshift/rook/pull/134

Comment 9 Michael Adam 2020-10-13 08:26:12 UTC
re-adding acks after changing component

Comment 10 Michael Adam 2020-10-13 08:26:57 UTC
POST since the rook patch exists.

Please clone to documentation for steps 2 and 3.

Comment 16 Neha Berry 2020-10-21 06:29:19 UTC
Moving to Rachael as she is already working on other external mode upgrade bugs and all are related to one another.

Comment 20 Mudit Agarwal 2020-10-29 06:54:53 UTC
Marking requires_doc_text to '-' as we have a separate doc BZ

Comment 23 errata-xmlrpc 2020-12-17 06:24:38 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 (Moderate: Red Hat OpenShift Container Storage 4.6.0 security, bug fix, enhancement update), 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-2020:5605

Comment 24 Red Hat Bugzilla 2023-09-15 00:48:59 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


Note You need to log in before you can comment on or make changes to this bug.