[Bug 1925347] Re: ceph-osd fails to start with ProtectClock=true

[James Page]

Test packages in:

  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3535

for any impacted Hirsute users (however don't expect to many of those
and the backport to the Wallaby UCA has picked this change up and a
transient patch for the backporter).

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

Title:
  ceph-osd fails to start with ProtectClock=true

Status in ceph package in Ubuntu:
  In Progress
Status in ceph source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  ceph-osd daemon is unable to start on fresh installs or post upgrade

  [Test Case]
  Deploy ceph with OSD units
  ceph-osd will fail to start

  [Regression Risk]
  Reverts ceph to its pre-pacific configuration for this option.

  [Original Bug Report]
  Ceph Pacific
  Ubuntu 20.04 (but 21.04 has the same change)

  Upstream pull: https://github.com/ceph/ceph/pull/40845
  Upstream issue: https://tracker.ceph.com/issues/50347

  Upstream enabled ProtectClock=true as part of a change to reduce
  permissions needed for daemons - however this has the side effect of
  disabling access to block devices, which is needed for the ceph-osd
  daemon (at least).

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