Actions
Bug #68035
closed`ceph-volume lvm zap` should call `ceph-bluestore-tool zap-device`
% Done:
0%
Source:
Backport:
squid
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Tags (freeform):
backport_processed
Merge Commit:
Fixed In:
v19.3.0-5160-g06708cb18c
Released In:
v20.2.0~1942
Upkeep Timestamp:
2025-11-01T01:30:45+00:00
Description
BlueStore now writes its metadata at multiple offset on devices [1].
It means `ceph-volume lvm zap` doesn't remove BlueStore signature altogether.
This can confuse ceph-volume when redeploying an OSD on a previously zapped device because there is still old BlueStore metadata on it.
ceph-volume should call `ceph-bluestore-tool zap-device` [2] in addition to the existing calls when wiping a device.
[1] https://github.com/ceph/ceph/pull/55374
[2] https://github.com/ceph/ceph/pull/59632
Updated by Guillaume Abrioux over 1 year ago
- Status changed from In Progress to Fix Under Review
Updated by Guillaume Abrioux over 1 year ago
- Status changed from Fix Under Review to Pending Backport
Updated by Upkeep Bot over 1 year ago
- Copied to Backport #68220: squid: `ceph-volume lvm zap` should call `ceph-bluestore-tool zap-device` added
Updated by Guillaume Abrioux over 1 year ago
- Status changed from Pending Backport to Resolved
Updated by Upkeep Bot 8 months ago
- Merge Commit set to 06708cb18c9c9d4cc1c6d8169ea2e72415d8e064
- Fixed In set to v19.3.0-5160-g06708cb18c9
- Upkeep Timestamp set to 2025-07-10T12:15:21+00:00
Updated by Upkeep Bot 8 months ago
- Fixed In changed from v19.3.0-5160-g06708cb18c9 to v19.3.0-5160-g06708cb18c
- Upkeep Timestamp changed from 2025-07-10T12:15:21+00:00 to 2025-07-14T20:10:45+00:00
Updated by Upkeep Bot 5 months ago
- Released In set to v20.2.0~1942
- Upkeep Timestamp changed from 2025-07-14T20:10:45+00:00 to 2025-11-01T01:30:45+00:00
Actions