[Bug 1767087] Re: ceph-volume: block device permissions sometimes not set on initial activate call

[James Page]

I'm not sure this is a packaging bug; the LVM layout implemented in the
ceph-osd charm is specific to the charm - it might represent some sort
of best practice that's worth encoding for all but that's not a given
right now.

** Also affects: charm-ceph-osd
   Importance: Undecided
       Status: New

** Changed in: charm-ceph-osd
       Status: New => In Progress

** Changed in: charm-ceph-osd
   Importance: Undecided => High

** Changed in: charm-ceph-osd
     Assignee: (unassigned) => James Page (james-page)

** Changed in: charm-ceph-osd
    Milestone: None => 18.05

** Changed in: ceph (Ubuntu)
       Status: In Progress => Incomplete

-- 
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/1767087

Title:
  ceph-volume: block device permissions sometimes not set on initial
  activate call

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

Bug description:
  When using bluestore or filestore with a separate journal device, we
  often see that the ceph-osd daemon crashes on activation with a
  'permission denied' error on the link to the block device supporting
  the particular component of the OSD (bluestore block/wal/db or journal
  device for filestore).

  chown -R ceph:ceph /dev/dm-X fixes the issue and the osd can then be
  started; I've also not seen this issue occur during a normal reboot
  (as the permissions are re-asserted by ceph-volume as OSD's are
  started up).

  Hunch is something udev-y is racing with ceph-volume on the initial
  activiate call but not tracked it down yet.

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