Bug 1633508 - default `osd_objectstore` to bluestore
Summary: default `osd_objectstore` to bluestore
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 3.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 3.2
Assignee: Sébastien Han
QA Contact: Parikshith
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-27 08:00 UTC by Sébastien Han
Modified: 2019-01-03 19:02 UTC (History)
9 users (show)

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:
Clone Of:
Environment:
Last Closed: 2019-01-03 19:01:53 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 3172 0 None closed default: use bluestore as default object store 2020-09-09 16:48:18 UTC
Red Hat Product Errata RHBA-2019:0020 0 None None None 2019-01-03 19:02:06 UTC

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