Bug 1388885 - [ceph-ansible] OSD creation of colocated encrypted OSD fails using ceph-ansible
Summary: [ceph-ansible] OSD creation of colocated encrypted OSD fails using ceph-ansible
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat Storage
Component: ceph-ansible
Version: 2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 2
Assignee: Andrew Schoen
QA Contact: Vasishta
URL:
Whiteboard:
Depends On:
Blocks: 1366808
TreeView+ depends on / blocked
 
Reported: 2016-10-26 11:11 UTC by Tejas
Modified: 2016-11-22 23:42 UTC (History)
11 users (show)

Fixed In Version: ceph-ansible-1.0.5-39.el7scon
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-22 23:42:10 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2817 0 normal SHIPPED_LIVE ceph-iscsi-ansible and ceph-ansible bug fix update 2017-04-18 19:50:43 UTC

Comment 2 Christina Meno 2016-10-26 15:34:54 UTC
Tejas,

Does this fail when dmcrypt_journal_collocation: false?

Comment 3 Andrew Schoen 2016-10-27 21:31:17 UTC
I believe I found a commit upstream that will resolve this problem.

https://github.com/ceph/ceph-ansible/commit/f162db1202a050d363820fc838e7df41ff9ce3d8

That commit is also mentions fixing this BZ https://bugzilla.redhat.com/show_bug.cgi?id=1376283

In short, what's happening is that the 'fail if ceph-disk cannot create an OSD' task is not being properly skipped when ceph-ansible is skipping other tasks related to other OSD scenarios. This specific task throws a syntax error in 1.9.4 because the variable used in it's when clause is not defined.

Comment 4 Andrew Schoen 2016-10-27 21:41:16 UTC
I've pushed a wip-bz-1388885 branch downstream with that commit cherry-picked into it to use for testing.

Comment 8 errata-xmlrpc 2016-11-22 23:42:10 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-2016:2817


Note You need to log in before you can comment on or make changes to this bug.