[Bug 1631328] Re: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration"

[Martin Pitt]

> This is a little chicken and egg - the ceph-common package configures
the ceph/ceph user/group, however udev notices the new rule file prior
to that happening....

udev uses inotify to pick up the new rule, but in order to actually
"run" the rule the handled device must either be removed and added or
udevadm trigger'ed (like in comment #8). So the postinst shold do that
after creating the groups.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1631328

Title:
  ceph-osd stays blocked on Yakkety: "No block devices detected using
  current configuration"

Status in ceph package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in ceph-osd package in Juju Charms Collection:
  Invalid

Bug description:
  The "ceph/default," "ceph_radosgw/simple_nonha" and "ceph/harden" mojo
  specs @ Yakkety are failing like so:

  Units are consistently blocked in Juju status:
  ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration"

  Snippets from ceph-osd unit syslog:
  mkjournal error creating journal on /var/lib/ceph/tmp/mnt.W59Jhd/journal: (13) Permission denied

  Oct  7 03:13:30 juju-osci-sv13-machine-4 systemd[1]: Failed to start
  Ceph disk activation: /dev/vdb1.

  See:

  http://pastebin.ubuntu.com/23288515/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1631328/+subscriptions