Ceph block device permission gets wrongly reverted by udev
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceph OSD Charm |
Won't Fix
|
Undecided
|
Ponnuvel Palaniyappan | ||
ceph (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
When creating OSD block devices, ceph-volume correctly sets the ownership to ceph:ceph. But when osd-encrypt is enabled before the cluster is deployed by Juju, udevadm reverts the permission back to root:disk.
A reproducer is:
Deploy a Mimic or Nautilus Ceph cluster using Juju (A bare-bones Ceph cluster using sts-bundles is sufficient). Then immediately after (before Juju completes the deployment), do
juju config ceph-osd osd-encrypt=True
Then the OSD units end up in blocked with "No block devices detected using current configuration".
This is caused by [0]
udevadm trigger --subsystem-
executed by ceph-osd charm.
This looks ery similar issue that's been fixed in the past [1]. However, the fix proposed there doesn't work here.
[0] https:/
[1] https:/
Changed in charm-ceph-osd: | |
status: | New → Confirmed |
assignee: | nobody → Ponnuvel Palaniyappan (pponnuvel) |
Changed in charm-ceph-osd: | |
status: | Confirmed → In Progress |
Changed in charm-ceph-osd: | |
status: | In Progress → Won't Fix |
Changed in ceph (Ubuntu): | |
status: | New → Won't Fix |
James' comment in [0] neatly describes the problem except it's not clear why the same fix isn't working in this situation.
[0] https:/ /bugs.launchpad .net/charm- ceph-osd/ +bug/1767087/ comments/ 2