Bug 2226662 - [Ceph 7.0] CephObjectStoreTool not reading type metadata label [NEEDINFO]
Summary: [Ceph 7.0] CephObjectStoreTool not reading type metadata label
Keywords:
Status: NEW
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 7.1
Assignee: Adam Kupczyk
QA Contact: Pawan
URL:
Whiteboard:
Depends On: 2226657
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-26 06:39 UTC by Santosh Pillai
Modified: 2023-08-10 05:00 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2226657
Environment:
Last Closed:
Embargoed:
sapillai: needinfo? (akupczyk)

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-7083 0 None None None 2023-07-26 06:41:42 UTC

Description Santosh Pillai 2023-07-26 06:39:22 UTC 
+++ This bug was initially created as a clone of Bug #2226657 +++

Description of problem:
`ceph-bluestore-tool bluefs-bdev-expand --path /var/lib/ceph/osd/ceph-0` fails to read the bluestore type

Error:
`inferring bluefs devices from bluestore path
expected bluestore, but type is`

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


How reproducible:


Steps to Reproduce:
1.Deploy rook using downstream ceph (commit: b53d9dfff6b1021fbab8e28f2b873d7d49cf5665)
2.Observe the osd creation flow

Actual results:The init container for `expand-bluefs` fails
sh-5.1# ceph-bluestore-tool bluefs-bdev-expand --path  /var/lib/ceph/osd/ceph-0 --log-level 30
inferring bluefs devices from bluestore path
expected bluestore, but type is 
sh-5.1#

Expected results: The command should not fail.



Additional info: BZ

--- Additional comment from INVALID USER on 2023-07-26 06:33:47 UTC ---

This bug report has Keywords: Regression or TestBlocker.

Since no regressions or test blockers are allowed between releases, it is being proposed as a blocker for this release.

Please resolve \triage ASAP.
Note You need to log in before you can comment on or make changes to this bug.