Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1696691 - [CEE/SD] 'ceph osd in any' marks all osds 'in' even if the osds are removed completely from the Ceph cluster.
Summary: [CEE/SD] 'ceph osd in any' marks all osds 'in' even if the osds are removed c...
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RADOS
Version: 3.2
Hardware: x86_64
OS: Linux
Target Milestone: rc
: 4.0
Assignee: Brad Hubbard
QA Contact: ceph-qe-bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2019-04-05 12:32 UTC by Ashish Singh
Modified: 2019-04-16 07:06 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Ceph Project Bug Tracker 39154 None None None 2019-04-09 08:14:03 UTC

Description Ashish Singh 2019-04-05 12:32:35 UTC
* Description of problem:
Running 'ceph osd in any' on a Ceph cluster marks all historic osd's 'in' which were once part of Ceph cluster.

* Version-Release number of selected component (if applicable):
RHCS 3.2z1

* How reproducible:

* Steps to Reproduce:
1. Run the following commands to remove an osd permanently from the Ceph cluster :
 - systemctl stop ceph-osd@1
 - ceph osd out 1
 - ceph osd crush remove osd.1
 - ceph auth del osd.1
 - ceph osd rm 1
 - umount /var/lib/ceph/osd/ceph-1
 - ceph-disk zap /dev/sdb (remove Ceph partition from the device as well)

2. After some time run command :
   # ceph osd in any

3. The osd.1 is marked 'down+in'

* Actual results:
osd's are marked 'in' even if they are removed permanently

* Expected results:
If the osd is removed permanently it should not be started.

* Additional info:

Note You need to log in before you can comment on or make changes to this bug.