Actions
Feature #44783
closedc-v's batch report doesn't show if the disk is going to be encrypted
% Done:
0%
Tags (freeform):
Merge Commit:
Fixed In:
v16.0.0-6063-g239c4bc8f3
Released In:
v16.2.0~1197
Upkeep Timestamp:
2025-07-15T01:16:47+00:00
Description
/usr/sbin/ceph-volume lvm batch --no-auto /dev/vdb --dmcrypt --report --format json
gives
{
"changed": true,
"osds": [
{
"block.db": {},
"data": {
"human_readable_size": "24.00 GB",
"parts": 1,
"path": "/dev/vdb",
"percentage": 100.0,
"size": 24
}
}
],
"vgs": []
}
which is missing the `encrypted` flag.
Updated by Jan Fajerski almost 6 years ago
- Subject changed from c-v's report doesn't show if the disk is going to be encrypted to c-v's batch report doesn't show if the disk is going to be encrypted
Updated by Jan Fajerski almost 6 years ago
- Tracker changed from Bug to Feature
Changing this to a feature.
I'd like input on what you'd expect. An encrypted, but where? Under the 'data' key, under the OSD key? Should be be false in case of unencrypted or missing?
I'd propose an new 'encrypted' key under 'data' that is either false or true.
Updated by Joshua Schmid almost 6 years ago
I assume that --dmcrypt is a block key that will affect all provided disks.
If that's the case, it would suffice to put it one layer above, on the same level as "changed" and "osds"
I don't know how c-v treat external db/wals when this flag is provided. If these LVs are not encrypted we might be better off, being more granular by putting it into the 'data' struct.
Updated by Kiefer Chang almost 6 years ago
- Related to Feature #44625: cephadm: test dmcrypt added
Updated by Jan Fajerski over 5 years ago
- Status changed from New to Resolved
- Pull request ID set to 34740
Updated by Upkeep Bot 8 months ago
- Merge Commit set to 239c4bc8f3c14f892656264789217b6b80e12982
- Fixed In set to v16.0.0-6063-g239c4bc8f3
- Released In set to v16.2.0~1197
- Upkeep Timestamp set to 2025-07-15T01:16:47+00:00
Actions