Actions
Bug #55167
closedceph-volume lvm new-db does not create encrypted devices
% Done:
0%
Source:
Tags:
backport_processed
Backport:
reef, quincy, pacific
Regression:
No
Severity:
3 - minor
Reviewed:
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.
Updated by Guillaume Abrioux about 2 years ago
- Status changed from New to In Progress
- Assignee set to Marius Schiffer
Updated by Igor Fedotov about 1 year ago
Updated by Igor Fedotov about 1 year ago
- Assignee changed from Marius Schiffer to Igor Fedotov
- Backport set to reef, quincy, pacific
Updated by Igor Fedotov 9 months ago
- Pull request ID changed from 50429 to 50427
Updated by Igor Fedotov 9 months ago
- Status changed from In Progress to Pending Backport
Updated by Backport Bot 9 months ago
- Copied to Backport #62358: reef: ceph-volume lvm new-db does not create encrypted devices added
Updated by Backport Bot 9 months ago
- Copied to Backport #62359: quincy: ceph-volume lvm new-db does not create encrypted devices added
Updated by Backport Bot 9 months ago
- Copied to Backport #62360: pacific: ceph-volume lvm new-db does not create encrypted devices added
Updated by Guillaume Abrioux 8 months ago
- Status changed from Pending Backport to Resolved
Actions