Actions
Bug #51869
openrollback on failure to create raw OSD leaves BlueStore header on disk
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When provisioning a disk (using raw mode) fails and ceph-volume rolls back creation of an OSD, the disk is still left with partial valid BlueStore data on the disk. Because of this, future attempts to provision the disk will fail. The disk should be wiped during rollback. I think wiping the first 4 512-byte blocks (2048 bytes) should be sufficient.
No data to display
Actions