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

[OpenStack Infra]

Reviewed:  https://review.openstack.org/567198
Committed: https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=35ad3de4f289e68f4d974e1bb25d00723f55cd12
Submitter: Zuul
Branch:    master

commit 35ad3de4f289e68f4d974e1bb25d00723f55cd12
Author: James Page <james.page at ubuntu.com>
Date:   Wed May 9 12:36:00 2018 +0100

    ceph-volume: Install charm specific udev rules
    
    Ensure that LV's created using the LVM layout implemented
    by this charm are correctly owned by the ceph user and group,
    ensuring that ceph-osd processes can start correctly at all
    times.
    
    Change-Id: I23ea51e3bffe7207f75782c5f34b796e9eed2c80
    Closes-Bug: 1767087


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

-- 
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 Committed
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