Bug 1499136 - ceph-ansible will exit with 0 with no OSDs up
Summary: ceph-ansible will exit with 0 with no OSDs up
Keywords:
Status: CLOSED DUPLICATE of bug 1541152
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 2.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 3.1
Assignee: Sébastien Han
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
: 1471826 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-06 08:02 UTC by Giulio Fidente
Modified: 2018-02-22 10:09 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-22 10:09:39 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible issues 1686 0 None None None 2017-10-06 08:02:40 UTC

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 ***
Note You need to log in before you can comment on or make changes to this bug.