Single Storage Pool Cannot be Used by multiple storage endpoints "no available machine matches constraints"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Undecided
|
Unassigned | ||
Ceph OSD Charm |
Invalid
|
Medium
|
Unassigned | ||
charms.ceph |
Invalid
|
Medium
|
Unassigned |
Bug Description
juju create-storage-pool nvme-osd-devices maas tags=ssd
juju create-storage-pool nvme-bluestore-wal maas tags=optane
In a bundle using this works:
storage:
osd-devices: 'nvme-osd-devices'
bluestore
#
this does not:
storage:
osd-devices: 'nvme-osd-devices'
bluestore
bluestore-db: 'nvme-bluestore
19 down pending xenial No available machine matches constraints: [('interfaces', ['ceph-
All spaces are there and configured on respective machines (commenting out the last storage binding proved that spaces are irrelevant here):
https:/
Changed in charms.ceph: | |
status: | New → Triaged |
Changed in charm-ceph-osd: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in charms.ceph: | |
importance: | Undecided → Medium |
This behavior affects charm-ceph-osd when wal and db need to be collocated.
To work around this issue, db needs to use the wal storage endpoint resolution.
https:/ /review. openstack. org/#/q/ topic:fe- collocate- if-db-unspecifi ed+(status: open+OR+ status: merged)