Bug 1388885
| Summary: | [ceph-ansible] OSD creation of colocated encrypted OSD fails using ceph-ansible | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Storage Console | Reporter: | Tejas <tchandra> |
| Component: | ceph-ansible | Assignee: | Andrew Schoen <aschoen> |
| Status: | CLOSED ERRATA | QA Contact: | Vasishta <vashastr> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2 | CC: | adeza, aschoen, ceph-eng-bugs, gmeno, kdreyer, kurs, nthomas, sankarshan, seb, tchandra, vashastr |
| Target Milestone: | --- | ||
| Target Release: | 2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-ansible-1.0.5-39.el7scon | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-22 23:42:10 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1366808 | ||
|
Comment 2
Christina Meno
2016-10-26 15:34:54 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. I've pushed a wip-bz-1388885 branch downstream with that commit cherry-picked into it to use for testing. 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 |