Project

General

Profile

Actions
Copy link

Bug #50347

closed

systemd: `ceph-osd@.service` Failed with `ProtectClock=true`

Added by Wong Hoi Sing Edison about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Wong Hoi Sing Edison
Category:
-
Target version:
v17.0.0
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
v16.2.0
ceph-qa-suite:
Pull request ID:
40845
Crash signature (v1):
Crash signature (v2):

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

Related issues 2 (1 open — 1 closed)

Related to RADOS - Bug #50682: Pacific - OSD not starting after upgradeNew

Actions
Copied to Ceph - Backport #50381: pacific: systemd: `ceph-osd@.service` Failed with `ProtectClock=true`ResolvedNeha OjhaActions
Actions
Copy link
 #1

Updated by Neha Ojha about 3 years ago

  • Status changed from New to Fix Under Review
Actions
Copy link
 #2

Updated by Patrick Donnelly about 3 years ago

  • Assignee set to Wong Hoi Sing Edison
  • Priority changed from Normal to Urgent
Actions
Copy link
 #3

Updated by Patrick Donnelly about 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #4

Updated by Backport Bot about 3 years ago

  • Copied to Backport #50381: pacific: systemd: `ceph-osd@.service` Failed with `ProtectClock=true` added
Actions
Copy link
 #5

Updated by Neha Ojha almost 3 years ago

  • Related to Bug #50682: Pacific - OSD not starting after upgrade added
Actions
Copy link
 #6

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
Copy link

Also available in: Atom PDF