ceph osd does not support use of nvme devices
Bug #1858057 reported by
Aaron Blair
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| openstack-helm-infra |
Fix Committed
|
Undecided
|
Aaron Blair | ||
Bug Description
Currently ceph-osd uses hard coded regexes (i.e. '[0-9]*') for partition and device determination over the entire code base. This regex limits supported devices to those with alphabetic characters only, and is not able to handle devices that also have numbers within the device name (i.e. nvme0n1).
To determine disk device and partitions within ceph-osd, I recommend replacing the current use of static regexes with a set of common functions that can be updated more easily to support more exotic device types than standard sdx and hdx devices.
| description: | updated |
| Changed in openstack-helm-infra: | |
| assignee: | nobody → Aaron Blair (spyd3rweb) |
| status: | New → In Progress |
| Changed in openstack-helm-infra: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Aaron Blair (spyd3rweb) wrote | #1 |
To post a comment you must log in.
Fix Committed:
https:/
Recommend revisiting the following change to ceph-osd to re-establish _common.sh.tpl for common device and partition functions accross both ceph-disk and ceph-volume; as it stands, we're essentially tracking two code bases with an overlap in functions:
https:/