Bug 1476210
Summary: | [ceph-ansible]: Bluestore is configured by default on the OSD's | ||||||
---|---|---|---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Tejas <tchandra> | ||||
Component: | Ceph-Ansible | Assignee: | Sébastien Han <shan> | ||||
Status: | CLOSED ERRATA | QA Contact: | Tejas <tchandra> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | urgent | ||||||
Version: | 3.0 | CC: | adeza, aschoen, ceph-eng-bugs, ddharwar, gmeno, hnallurv, kdreyer, nthomas, sankarshan, seb, tchandra, tserlin | ||||
Target Milestone: | rc | Keywords: | Reopened | ||||
Target Release: | 3.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | RHEL: ceph-ansible-3.0.0-0.1.rc1.el7cp Ubuntu: ceph-ansible_3.0.0~rc4-2redhat1 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2017-12-05 23:38:03 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: | |||||||
Attachments: |
|
Description
Tejas
2017-07-28 09:50:27 UTC
Fixed in ceph-ansible-2.3.0-0.1.rc5.el7cp.noarch. *** Bug 1476856 has been marked as a duplicate of this bug. *** Created attachment 1307470 [details]
ansible playbook log
can I see your group_vars file? After a first look, the issue is that you need to set ceph_stable_release to luminous. I'll work on making this easier though, please try that in the meantime. FYI rc6 will make ceph_stable_release mandatory but I'm looking into automating the detection. I tried setting these options and this configured filestore as expected. ceph_stable: true ceph_stable_release: luminous Thanks, Tejas Verified on version ceph-ansible-3.0.0-0.1.rc8.1.el7cp.noarch 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-2017:3387 |