Bug 1637537 - ceph-ansible fails at TASK [ceph-validate : check if bluestore is supported by the selected ceph version]
Summary: ceph-ansible fails at TASK [ceph-validate : check if bluestore is supported b...
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: Rachana Patel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-09 12:48 UTC by Pratik Surve
Modified: 2019-01-03 19:02 UTC (History)
11 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:02:01 UTC
Embargoed:
prsurve: automate_bug+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 3205 0 None None None 2018-10-09 14:19:01 UTC
Red Hat Product Errata RHBA-2019:0020 0 None None None 2019-01-03 19:02:15 UTC

Comment 3 Andrew Schoen 2018-10-09 13:34:35 UTC 
The ceph_release variable is not being defined, which is why this failure is happening. Could you include your full configuration, playbook, inventory and full log.

Thanks,
Andrew
Comment 4 Andrew Schoen 2018-10-09 14:15:48 UTC 
I think this upstream PR should address the problem. We really shouldn't be doing version checks in ceph-validate anyway. If you do not run ceph-defaults and pass ceph_stable_release these will never pass anyway in ceph-validate.

https://github.com/ceph/ceph-ansible/pull/3205
Comment 5 Sébastien Han 2018-10-12 15:23:51 UTC 
Present in https://github.com/ceph/ceph-ansible/releases/tag/v3.2.0beta5
Comment 12 errata-xmlrpc 2019-01-03 19:02:01 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.