Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1640525

Summary: [Ceph-Ansible] Missing fourth and fifth scenarios in osds.yml.sample
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Persona non grata <nobody+410372>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED ERRATA QA Contact: Ameena Suhani S H <amsyedha>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1CC: amsyedha, aschoen, ceph-eng-bugs, ceph-qe-bugs, dsavinea, gmeno, nthomas, tchandra, tserlin, vashastr
Target Milestone: z2   
Target Release: 3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-ansible-3.2.36-1.el7cp Ubuntu: ceph-ansible_3.2.36-2redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-19 17:59:09 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 Persona non grata 2018-10-18 09:35:13 UTC 
Description of problem:
In this following link
https://github.com/ceph/ceph-ansible/blob/stable-3.1/group_vars/osds.yml.sample#L50
It tells that " You can use this option with First and Forth and Fifth OSDS scenario", but Forth and Fifth scenarios descriptions are not found in that osds.yml.sample.

Version-Release number of selected component (if applicable):
ceph-ansible-3.1.9-1.el7cp.noarch

How reproducible:
NA

Steps to Reproduce:
1.
2.
3.

Actual results:
Descriptions of forth and fifth OSDS scenarios are missing.

Expected results:

Descriptions of forth and fifth OSDS scenarios should be mentioned.

Additional info:
Comment 3 Sébastien Han 2018-11-07 11:54:52 UTC 
This is a leftover and the line should be removed.
Thanks
Comment 4 Noah Watkins 2018-11-16 01:06:54 UTC 
Merged upstream.
Comment 5 Giridhar Ramaraju 2019-08-05 13:11:14 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 6 Giridhar Ramaraju 2019-08-05 13:12:15 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 11 Ameena Suhani S H 2019-11-13 07:08:45 UTC 
Hi,
The issue is still seen in ceph-ansible-3.2.34-1.el7cp.noarch.
Moving to ASSIGNED state.
Comment 12 Vasishta 2019-11-13 11:13:54 UTC 
Commit [1] has fixes for this BZ which was not backported

[1] https://github.com/ceph/ceph-ansible/commit/64dee9be0c8e6ce4cfe01bf7c9956efacc195ba4#diff-6811c0962f7a6681615e383130868fa3

I think above commit needs to be backported to stable-3.2 branch.


Regards,
Vasishta Shastry
QE, Ceph
Comment 17 Ameena Suhani S H 2019-11-21 09:56:31 UTC 
Verified using ceph-ansible-3.2.36-1.el7cp.noarch.
Moving to "VERIFIED' state
Comment 19 errata-xmlrpc 2019-12-19 17:59:09 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:4353