Bug #23053: ceph-volume lvm prepare option --crush-device-class not recognized - ceph-volume - Ceph

Actions

Copy link

Bug #23053

closed

ceph-volume lvm prepare option --crush-device-class not recognized

Added by Kenneth Waegeman about 6 years ago. Updated about 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Target version:

% Done:

Source:

Community (user)

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

Ceph - v12.2.2

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

From
http://docs.ceph.com/docs/master/ceph-volume/lvm/prepare/#crush-device-class :

ceph-volume lvm prepare --bluestore --data vg/lv --crush-device-class foo

but I get:

[root@ceph001 ~]# ceph-volume lvm prepare --bluestore --data /dev/sdn --crush-device-class foo
usage: ceph-volume lvm prepare [-h] [--journal JOURNAL] --data DATA
[--journal-size GB] [--bluestore] [--filestore]
[--osd-id OSD_ID] [--osd-fsid OSD_FSID]
[--block.db BLOCK_DB] [--block.wal BLOCK_WAL]
ceph-volume lvm prepare: error: unrecognized arguments: --crush-device-class foo

Actions

Copy link

Updated by Alfredo Deza about 6 years ago

What version of Ceph are you using? We just added this and your pointing the docs to the master link

Actions

Copy link

Updated by Kenneth Waegeman about 6 years ago

Hey, We are running Luminous 12.2.2. I also saw it here http://docs.ceph.com/docs/luminous/ceph-volume/lvm/prepare/#crush-device-class
Thank you!

Actions

Copy link

Updated by Andrew Schoen about 6 years ago

Status changed from New to Closed

Kenneth Waegeman wrote:

Hey, We are running Luminous 12.2.2. I also saw it here http://docs.ceph.com/docs/luminous/ceph-volume/lvm/prepare/#crush-device-class
Thank you!

It's in the luminous docs because this was just added to 12.2.3. Could you try 12.2.3 and if you have the same issue please reopen this issue. Thanks!

Actions

Copy link

Updated by Kenneth Waegeman about 6 years ago

I can now create the osd with a device class, but it doesn't result in the expected behaviour.

I can see the class overwrite in pvs output:
ceph.crush_device_class=ssd,ceph.encrypted=1,ceph.osd_fsid=7bceb016-42df-408a-b171-6a84f8fb9d4b,ceph.osd_id=18,ceph.type=block

but the new osd is listed in the crushmap as an hdd :
18 hdd 3.63869 osd.18 up 1.00000 1.00000

so it looks like the pv attributes are not checked?

Thanks again!

Actions

Copy link