Bug 1541071

Summary: [ceph-ansible] dedicated journal and dmcrypt enabled scenarios are failing
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Ken Dreyer (Red Hat) <kdreyer>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED ERRATA QA Contact: Vidushi Mishra <vimishra>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.0CC: adeza, aschoen, ceph-eng-bugs, gabrioux, gmeno, hnallurv, kdreyer, nthomas, rperiyas, sankarshan, shan, tchandra, vashastr, vimishra, vpoliset
Target Milestone: z1   
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-ansible-3.0.19-1.el7cp Ubuntu: ceph-ansible_3.0.19-2redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1536098 Environment:
Last Closed: 2018-03-08 15:52:40 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: 1536098    

Comment 2 Vidushi Mishra 2018-02-06 11:01:51 UTC 
Tested for the below OSD scenarios:

1.Dedicated journal 
2.Dedicated journal + dmcrypt
3.collocated journal + dmcrypt
4.osd_auto_discovey=true + dmcrypt_journal_collocation='true'
5.Collocated Journal
6.osd_auto_discovey=true + journal_collocation='true'

Not observing the issue in ceph-ansible-3.0.23-1.el7cp.noarch. Will move BZ o verified, once ON_QA.
Comment 3 Ramakrishnan Periyasamy 2018-02-07 07:24:08 UTC 
Hi Ken,

Can you please move this bug to ON_QA, so that QE can move this to verified state.

--Ram
Comment 5 Vidushi Mishra 2018-02-08 06:01:21 UTC 
Moving BZ to verified for ceph-ansible-3.0.23-1.el7cp.noarch.
Comment 6 Ramakrishnan Periyasamy 2018-02-08 11:54:40 UTC 
clearing needinfo tag.
Comment 9 errata-xmlrpc 2018-03-08 15:52:40 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-2018:0474