Actions
Bug #50347
closedsystemd: `ceph-osd@.service` Failed with `ProtectClock=true`
% Done:
0%
Description
Ceph 16.2.0 Pacific introduce following new systemd restriction:
ProtectClock=true
ProtectHostname=true
ProtectKernelLogs=true
RestrictSUIDSGID=true
BTW, `ceph-osd@.service` failed with `ProtectClock=true` unexpectly, also see:
- <https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/thread/TNBGGNN6STGDKARAQTQCIPTU4KLIVJQV/>
- <https://serverfault.com/questions/1059317/bluestore-var-lib-ceph-osd-ceph-2-block-read-bdev-label-failed-to-open-var-l>
This PR intruduce:
- Remove `ProtectClock=true` for our systemd service templates
Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
Updated by Neha Ojha about 3 years ago
- Status changed from New to Fix Under Review
Updated by Patrick Donnelly about 3 years ago
- Assignee set to Wong Hoi Sing Edison
- Priority changed from Normal to Urgent
Updated by Patrick Donnelly about 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot about 3 years ago
- Copied to Backport #50381: pacific: systemd: `ceph-osd@.service` Failed with `ProtectClock=true` added
Updated by Neha Ojha about 3 years ago
- Related to Bug #50682: Pacific - OSD not starting after upgrade added
Updated by Loïc Dachary almost 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions