Bug 1499136

Summary:	ceph-ansible will exit with 0 with no OSDs up
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Giulio Fidente <gfidente>
Component:	Ceph-Ansible	Assignee:	Sébastien Han <shan>
Status:	CLOSED DUPLICATE	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.4	CC:	adeza, aschoen, ceph-eng-bugs, gmeno, jpichon, kdreyer, nthomas, sankarshan
Target Milestone:	rc
Target Release:	3.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-22 10:09:39 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:

Description Giulio Fidente 2017-10-06 08:02:41 UTC

Description of problem:
There are chances that ceph-ansible will exit with 0 even though no OSDs are up at the end of the deployment.


Version-Release number of selected component (if applicable):
ceph-ansible-3.0.0-0.rc17.1.el7.noarch


Expected results:
At least for the initial deployment, we should make sure that all devices given to ceph-ansible are enabled or fail the deployment.

Comment 3 Giulio Fidente 2017-10-10 13:36:28 UTC

*** Bug 1471826 has been marked as a duplicate of this bug. ***

Comment 4 Sébastien Han 2017-10-12 13:58:35 UTC

This comes out of nowhere and at the end of the cycle, we never agreed to have this for 3.0, I'm pushing this to 3.1.
Thanks.

Comment 7 Giulio Fidente 2018-02-22 10:09:39 UTC


*** This bug has been marked as a duplicate of bug 1541152 ***