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

[Launchpad Bug Tracker]

This bug was fixed in the package ceph - 13.2.1+dfsg1-0ubuntu3

---------------
ceph (13.2.1+dfsg1-0ubuntu3) disco; urgency=medium

  * No-change rebuild for python3.7 as the default python3.

 -- Matthias Klose <doko at ubuntu.com>  Tue, 30 Oct 2018 19:25:09 +0100

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

-- 
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:
  Fix Released
Status in ceph package in Ubuntu:
  Fix Released

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