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 1633508

Summary:	default `osd_objectstore` to bluestore
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Sébastien Han <shan>
Component:	Ceph-Ansible	Assignee:	Sébastien Han <shan>
Status:	CLOSED ERRATA	QA Contact:	Parikshith <pbyregow>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.2	CC:	anharris, aschoen, ceph-eng-bugs, gmeno, hnallurv, kdreyer, nthomas, sankarshan, vumrao
Target Milestone:	rc
Target Release:	3.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-ansible-3.2.0-0.1.beta5.el7cp Ubuntu: ceph-ansible_3.2.0~beta5-2redhat1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-03 19:01:53 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 Sébastien Han 2018-09-27 08:00:18 UTC

Description of problem:

All tooling in Ceph is defaulting to use the bluestore objectstore for provisioning OSDs, there is no good reason for ceph-ansible to continue to default to filestore.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

OSDs get configured with filestore by default.

Expected results:

OSDs should be configured with bluestore by default.

Additional info:

Comment 3 Sébastien Han 2018-09-28 15:11:11 UTC

Merged upstream and will be in v3.2.0beta3

Comment 4 Sébastien Han 2018-10-02 20:15:24 UTC

https://github.com/ceph/ceph-ansible/releases/tag/v3.2.0beta3

Comment 10 errata-xmlrpc 2019-01-03 19:01:53 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/RHBA-2019:0020