Bug 1805643

Summary:	[RFE] purge-container-cluster: support OSDs with 3 digits
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Dariusz Wojewódzki <dwojewod>
Component:	Ceph-Ansible	Assignee:	Guillaume Abrioux <gabrioux>
Status:	CLOSED ERRATA	QA Contact:	Vasishta <vashastr>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.1	CC:	aschoen, ceph-eng-bugs, ceph-qe-bugs, dsavinea, gabrioux, gmeno, hyelloji, knortema, nthomas, rmandyam, tserlin, ykaul
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	4.1	Flags:	hyelloji: needinfo-
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	ceph-ansible-4.0.16-1.el8, ceph-ansible-4.0.16-1.el7	Doc Type:	Enhancement
Doc Text:	.`purge-container-cluster.yml` playbook now supports clusters with three-digit IDs Previously, `purge-container-cluster` only supported {product} clusters with up to 99 OSDs. This is because the playbook supported ceph-osd services with two-digit indices. With this update, you can properly purge clusters with three-digit IDs.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-19 17:32:27 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:	1816167

Description Dariusz Wojewódzki 2020-02-21 09:35:45 UTC

Description of problem:
purge-container-cluster can not stop ceph-osd services with 3 digit index


purge-container-cluster.yml playbook can find only OSDs service with just 2 numerals,  
I have with 3 and the playbook can not stop service’s and can’t remove vg. 

https://github.com/ceph/ceph-ansible/blob/36175435174cb3f135575155a46d1599a835e818/infrastructure-playbooks/purge-container-cluster.yml#L254


Version-Release number of selected component (if applicable):
ceph-ansible v 4.0.14-1

Comment 13 errata-xmlrpc 2020-05-19 17:32:27 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-2020:2231