Actions
Bug #57609
closedapplying osd service spec with size filter fails if there's tiny (KB-sized) block devices present
% Done:
0%
Source:
Tags:
backport_processed
Backport:
quincy,pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Description
This issue came up on a system with a 4KB virtual floppy disk drive.
ceph-volume inventory
gives:
Device Path Size rotates available Model name /dev/fd0 4.00 KB True False /dev/sda 50.00 GB True False Virtual disk /dev/sdb 50.00 GB True False Virtual disk /dev/sdc 50.00 GB True False Virtual disk /dev/sdd 50.00 GB True False Virtual disk
Doing a simple ceph orch apply osd --all-available-devices
works just fine, but service specs utilising size specifiers will fail to apply. For example:
service_id: at_least_8g service_type: osd placement: host_pattern: '*' spec: data_devices: size: '8G:'
Applying the above will give the following error in ceph log last cephadm
:
ceph.deployment.drive_group.DriveGroupValidationError: Failed to validate OSD spec "at_least_8g.data_devices": Unit 'KB' not supported
The problem is that the SizeMatcher class only understands MB, GB and TB. When presented with a disk whose size is expressed in KB, it doesn't know what to do with it.
Updated by Tim Serong over 1 year ago
- Status changed from New to Fix Under Review
- Pull request ID set to 48184
Updated by Adam King over 1 year ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot over 1 year ago
- Copied to Backport #57637: quincy: applying osd service spec with size filter fails if there's tiny (KB-sized) block devices present added
Updated by Backport Bot over 1 year ago
- Copied to Backport #57638: pacific: applying osd service spec with size filter fails if there's tiny (KB-sized) block devices present added
Updated by Adam King about 1 year ago
- Status changed from Pending Backport to Resolved
Actions