[Bug 1915705] Re: Ceph block device permission gets wrongly reverted by udev

[Ponnuvel Palaniyappan]

James Page suggested this might need to be done in the packaging as
well.

Once the fix is finalized in charm-ceph-osd, I'll update the udev rules
in debian/udev/95-ceph-osd-lvm.rules.

** Also affects: ceph (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1915705

Title:
  Ceph block device permission gets wrongly reverted by udev

Status in OpenStack ceph-osd charm:
  In Progress
Status in ceph package in Ubuntu:
  New

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-match=block --action=add

  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://github.com/openstack/charms.ceph/blob/master/charms_ceph/utils.py#L984
  [1] https://bugs.launchpad.net/charm-ceph-osd/+bug/1767087

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1915705/+subscriptions