ceph-osd fails to start with ProtectClock=true
Bug #1925347 reported by
James Page
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
Undecided
|
Unassigned | ||
Wallaby |
Fix Released
|
Undecided
|
Unassigned | ||
Xena |
Fix Released
|
Undecided
|
Unassigned | ||
ceph (Ubuntu) |
Fix Released
|
Critical
|
James Page | ||
Hirsute |
Fix Released
|
Critical
|
James Page |
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:/
Upstream issue: https:/
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).
CVE References
description: | updated |
Changed in ceph (Ubuntu Hirsute): | |
status: | New → In Progress |
importance: | Undecided → Critical |
assignee: | nobody → James Page (james-page) |
To post a comment you must log in.
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).