Project

General

Profile

Actions

Bug #46833

closed

simple (ceph-disk style) OSDs adopted by cephadm must not call `ceph-volume lvm activate`

Added by Tim Serong over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
cephadm
Target version:
% Done:

0%

Source:
Tags:
Backport:
octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The unit files created when adopting OSDs include a few chown calls to handle simple (ceph-disk style) OSDs, and also include a call to ceph-volume lvm activate, to handle LVM OSDs. The problem here is that ceph-volume lvm activate fails for simple OSDs, and this in turn causes the OSD to not start. Last time I was working on this (see https://tracker.ceph.com/issues/45129), I didn't hit this problem, but something must have changed in the meantime. Whether that's a new systemd version, or a slightly different error handling path, I'm not sure, but the point is it would be best if we only generated exactly the correct commands, depending on the type of OSD, rather than including both the chown and the ceph-volume lvm activate calls in all cases.

(This issue was originally reported downstream as https://bugzilla.suse.com/show_bug.cgi?id=1174594)


Related issues 1 (0 open1 closed)

Related to Orchestrator - Bug #45129: simple (ceph-disk) style OSDs adopted by cephadm don't start after rebootResolvedTim Serong

Actions
Actions #1

Updated by Tim Serong over 3 years ago

  • Related to Bug #45129: simple (ceph-disk) style OSDs adopted by cephadm don't start after reboot added
Actions #2

Updated by Tim Serong over 3 years ago

  • Status changed from New to In Progress
Actions #3

Updated by Tim Serong over 3 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 36463
Actions #4

Updated by Tim Serong over 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #5

Updated by Sebastian Wagner over 3 years ago

  • Status changed from Pending Backport to Resolved
  • Target version set to v15.2.5
Actions

Also available in: Atom PDF