Project

General

Profile

Actions
Copy link

Bug #55167

closed

ceph-volume lvm new-db does not create encrypted devices

Added by Marius Schiffer about 2 years ago. Updated 8 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Igor Fedotov
Target version:
-
% Done:

0%

Source:
Tags:
backport_processed
Backport:
reef, quincy, pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
50427
Crash signature (v1):
Crash signature (v2):

Description

If an OSD is created with --dmcrypt and later a DB or WAL device is added via ceph-volume new-db/new-wal, no LUKS device is created in the specified LV.
Instead the LV is used directly. Consequently, OSD activation fails as luksOpen fails.
During activation, ceph-volume wants to open the DB as an encrypted device, which it isn't. Manually creating the block.db symlink in the tmpfs allows starting.

Migrate also does not take encrypted devices into account.

Related issues 3 (0 open — 3 closed)

Copied to ceph-volume - Backport #62358: reef: ceph-volume lvm new-db does not create encrypted devicesResolvedIgor FedotovActions
Copied to ceph-volume - Backport #62359: quincy: ceph-volume lvm new-db does not create encrypted devicesResolvedIgor FedotovActions
Copied to ceph-volume - Backport #62360: pacific: ceph-volume lvm new-db does not create encrypted devicesResolvedIgor FedotovActions
Actions
Copy link

Also available in: Atom PDF