Bug 2187348 - [cee/sd][cephadm] Ceph orchestrator redeploys OSD with wrong dedicated DB size for non-collocated scenario
Summary: [cee/sd][cephadm] Ceph orchestrator redeploys OSD with wrong dedicated DB siz...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Volume
Version: 5.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 5.3z3
Assignee: Guillaume Abrioux
QA Contact: Manisha Saini
lysanche
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-17 13:34 UTC by Milind
Modified: 2023-07-17 13:39 UTC (History)
10 users (show)

Fixed In Version: ceph-16.2.10-168.el8cp
Doc Type: Bug Fix
Doc Text:
.The correct size is calculated for each database device in `ceph-volume` Previously, as of RHCS 4.3, `ceph-volume` would not make a single VG with all database devices inside, since each database device had its own VG. Due to this, the database size was calculated differently for each LV. With this release, the logic is updated to take into account the new database devices with LVM layout. The correct size is calculated for each database device.
Clone Of:
Environment:
Last Closed: 2023-05-23 00:19:11 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-6473 0 None None None 2023-04-17 13:35:49 UTC
Red Hat Product Errata RHBA-2023:3259 0 None None None 2023-05-23 00:19:41 UTC

Description Milind 2023-04-17 13:34:10 UTC
Description of problem:
Redeployment of the OSDs in non-collocated scenario results in wrongly configured 
DB size.

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

How reproducible:
Always

Steps to Reproduce:
1. Create a 5.3z2 cluster and create 4 OSDs with 4 disks with dedicated DB device on 2 disks having DBs for 2 OSD disk each.
2. make sure that OSDs are in managed state (default)
2. Remove the OSDs via `ceph orch osd rm --zap OSD.IDs
3. OSDs gets recreated with Wrong DB size

Actual results:
Wrong DB size gets assigned to OSDs DB

Expected results:
Dbs should get created corectly with correct size.

Comment 5 Milind 2023-04-18 11:45:07 UTC
Hi Adam,

yeah, it looks similar to me.
but here the customer also admitted that the same behavior is happening even after giving the block_db_size explicitly in spec file.

will that make any difference, if not then yeah both issues are same.

Regards
Milind Verma

Comment 24 errata-xmlrpc 2023-05-23 00:19:11 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.3 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:3259


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