Project

General

Profile

Bug #46134

ceph mgr should fail if it cannot add osd

Added by Deepika Upadhyay almost 4 years ago. Updated about 3 years ago.

Status:
Can't reproduce
Priority:
Low
Assignee:
-
Category:
orchestrator
Target version:
-
% Done:

0%

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

Description

strangely, after copying the ssh keys to remote host, when a new osd is added, the process executes without failure.

[deepika@x1cabon cephadm]$ sudo ./cephadm --image docker.io/ceph/ceph:v15.2.0 shell -c /etc/ceph/ceph.conf -k /etc/ceph/ceph.client.admin.keyring --fsid 110f6b2c-b254-11ea-9aa5-24ee9af1caac -- ceph orch daemon add osd vossi04:/dev/sda1
WARNING: The same type, major and minor should not be used for multiple devices.
WARNING: The same type, major and minor should not be used for multiple devices.
WARNING: The same type, major and minor should not be used for multiple devices.
WARNING: The same type, major and minor should not be used for multiple devices.

(though not correct to do) But when we try to see the available hosts after adding the osd we can't find the new host.

[deepika@x1cabon cephadm]$ sudo ./cephadm --image docker.io/ceph/ceph:v15.2.0 shell -c /etc/ceph/ceph.conf -k /etc/ceph/ceph.client.admin.keyring --fsid 110f6b2c-b254-11ea-9aa5-24ee9af1caac -- ceph orch device ls
WARNING: The same type, major and minor should not be used for multiple devices.
WARNING: The same type, major and minor should not be used for multiple devices.
WARNING: The same type, major and minor should not be used for multiple devices.
WARNING: The same type, major and minor should not be used for multiple devices.
HOST     PATH          TYPE   SIZE  DEVICE                                     AVAIL  REJECT REASONS                                          
x1cabon  /dev/nvme0n1  ssd    238G  SAMSUNG MZVLB256HBHQ-000L7_S4ELNF0M658498  False  LVM detected, Insufficient space (<5GB) on vgs, locked  

expected behaviour should be a failure to add osd if host is not available/configured.

History

#1 Updated by Sebastian Wagner almost 4 years ago

hm strange. did that host appear after a while?

#2 Updated by Deepika Upadhyay almost 4 years ago

Nope, cannot trace any process logs as well anywhere, appears to be just a log print.

#3 Updated by Sebastian Wagner about 3 years ago

  • Status changed from New to Can't reproduce

Also available in: Atom PDF