Bug 2121265 - (RHCS 6) MGR is not reporting the version label in the ceph_mon_metadata metric
Summary: (RHCS 6) MGR is not reporting the version label in the ceph_mon_metadata metric
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 4.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 6.0
Assignee: Prashant Dhange
QA Contact: skanta
Masauso Lungu
URL:
Whiteboard:
Depends On: 2008524
Blocks: 1933907 2008527 2126050
TreeView+ depends on / blocked
 
Reported: 2022-08-25 02:50 UTC by Prashant Dhange
Modified: 2023-03-20 18:58 UTC (History)
27 users (show)

Fixed In Version: ceph-17.2.3-22.el9cp
Doc Type: Bug Fix
Doc Text:
.The Prometheus metrics now reflect the correct Ceph version for all Ceph Monitors whenever requested Previously, the Prometheus metrics reported mismatched Ceph versions for Ceph Monitors when the monitor was upgraded. As a result, the active Ceph Manager daemon needed to be restarted to resolve this inconsistency. Additionally, the Ceph manager used to update the monitor metadata through the `handle_mon_map` parameter, which gets triggered when the monitors are removed or added from the cluster or the active `mgr` is restarted or `mgr` failsover.
Clone Of: 2008524
Environment:
Last Closed: 2023-03-20 18:57:23 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-5144 0 None None None 2022-08-25 02:54:56 UTC
Red Hat Product Errata RHBA-2023:1360 0 None None None 2023-03-20 18:58:04 UTC

Comment 46 errata-xmlrpc 2023-03-20 18:57:23 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 (Red Hat Ceph Storage 6.0 Bug Fix 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/RHBA-2023:1360


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