Project

General

Profile

Actions

Bug #54535

closed

ceph-volume doesn't abort osd creation if passed device has a FS

Added by Guillaume Abrioux about 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
High
Target version:
-
% Done:

0%

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

Description

similar to https://tracker.ceph.com/issues/54376

when a device with a FS on it is passed, ceph-volume will erase everything and create an OSD anyway.


Related issues 3 (0 open3 closed)

Copied to ceph-volume - Backport #55261: pacific: ceph-volume doesn't abort osd creation if passed device has a FSResolvedActions
Copied to ceph-volume - Backport #55262: quincy: ceph-volume doesn't abort osd creation if passed device has a FSResolvedActions
Copied to ceph-volume - Backport #55263: octopus: ceph-volume doesn't abort osd creation if passed device has a FSResolvedActions
Actions #1

Updated by Guillaume Abrioux about 2 years ago

  • Status changed from In Progress to Fix Under Review
Actions #2

Updated by Guillaume Abrioux about 2 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #3

Updated by Backport Bot about 2 years ago

  • Copied to Backport #55261: pacific: ceph-volume doesn't abort osd creation if passed device has a FS added
Actions #4

Updated by Backport Bot about 2 years ago

  • Copied to Backport #55262: quincy: ceph-volume doesn't abort osd creation if passed device has a FS added
Actions #5

Updated by Backport Bot about 2 years ago

  • Copied to Backport #55263: octopus: ceph-volume doesn't abort osd creation if passed device has a FS added
Actions #6

Updated by Guillaume Abrioux almost 2 years ago

  • Pull request ID set to 45349
Actions #7

Updated by Guillaume Abrioux almost 2 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF