Bug 1952193 - Upgraded from nautilus to pacific - OSD(s) reporting legacy (not per-pool) BlueStore omap usage stats
Summary: Upgraded from nautilus to pacific - OSD(s) reporting legacy (not per-pool) Bl...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 5.0
Assignee: Neha Ojha
QA Contact: Manohar Murthy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-21 17:46 UTC by Vasishta
Modified: 2021-08-30 08:30 UTC (History)
8 users (show)

Fixed In Version: ceph-16.2.0-12.el8cp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-30 08:29:54 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-793 0 None None None 2021-08-19 16:42:03 UTC
Red Hat Product Errata RHBA-2021:3294 0 None None None 2021-08-30 08:30:16 UTC

Description Vasishta 2021-04-21 17:46:28 UTC 
Description of problem:
when Cluster upgraded from nautilus to pacific (RHCS 4.x to RHCS 5.x) cluster status says OSD(s) reporting legacy (not per-pool) BlueStore omap usage stats

Version-Release number of selected component (if applicable):
16.2.0-10.el8cp

How reproducible:
Tried once

Steps to Reproduce: (what we followed)
1. Configure a 4.x baremetal cluster
2. Migrate it to containerized cluster
3. Upgrade cluster to 5.x
4. run cephadm-adopt playbook

Actual results:
(check further comments)

Expected results:
No warnings/ cluster status should be apt

Additional info:
Tentatively selecting component as RADOS, feel free to change to ceph-ansible if ceph-ansible is missing any step
Comment 11 errata-xmlrpc 2021-08-30 08:29:54 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 5.0 bug fix and enhancement), 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-2021:3294
Note You need to log in before you can comment on or make changes to this bug.