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

[Aurelien Lourot]

This fixed the bug for me, thanks! To reproduce/validate I deploy Ceph
Pacific on Hirsute s390x machines using this Juju bundle. [0]

If I leave the software source as `distro`, I hit the bug, i.e. ceph-osd fails to start with:
bluestore(/var/lib/ceph/osd/ceph-0/block) _read_bdev_label failed to open /var/lib/ceph/osd/ceph-0/block: (1) Operation not permitted

If I then change the software source to `distro-proposed`, this ends up
installing ceph-osd 16.2.1-0ubuntu0.21.04.1 and Ceph works as expected.

[0] https://github.com/openstack-charmers/openstack-
bundles/blob/master/development/ceph-base-hirsute-pacific/bundle.yaml


** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute

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

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