Bug 1696691

Summary: [CEE/SD] 'ceph osd in any' marks all osds 'in' even if the osds are removed completely from the Ceph cluster.
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Ashish Singh <assingh>
Component: RADOSAssignee: Brad Hubbard <bhubbard>
Status: CLOSED ERRATA QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2CC: bhubbard, ceph-eng-bugs, dzafman, edonnell, jdurgin, kchai, kjosy, mmurthy, mrussell, nojha, pamadio, sknauss, tchandra, tpetr, tserlin
Target Milestone: rc   
Target Release: 3.3   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.12-16.el7cp Ubuntu: ceph_12.2.12-15redhat1xenial Doc Type: Bug Fix
Doc Text:
.`ceph osd in any` no longer marks permanently removed OSDs as `in` Previously, running the `ceph osd in any` command on a Red Hat Ceph Storage cluster marked all historic OSDs that were once part of the cluster as `in`. With this update, `ceph osd in any` no longer marks permanently removed OSDs as `in`.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-21 15:10:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1726135    

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:
Always

* 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:
NA

Comment 22 errata-xmlrpc 2019-08-21 15:10:49 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:2538