Project

General

Profile

Actions

Bug #51028

closed

device zap doesn't perform any checks

Added by Paul Cuzner almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
orchestrator
Target version:
% Done:

0%

Source:
Tags:
ux
Backport:
Regression:
No
Severity:
2 - major
Reviewed:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

An orch device zap <host> <dev> doesn't perform any validation checking and can expose the admin to a situation where the wrong device is zapped removing an active OSD from the cluster.

I would suggest that to remediate;
- orchestrator should validate the hostname exists and it's status is empty (i.e. host is available)
- cephadm should check the device is not part of an active osd


Related issues 1 (0 open1 closed)

Related to Orchestrator - Bug #52919: ceph orch device zap validation can result in osd issues and problematic error messagesResolvedPaul Cuzner

Actions
Actions

Also available in: Atom PDF