Bug 1541071 - [ceph-ansible] dedicated journal and dmcrypt enabled scenarios are failing
Summary: [ceph-ansible] dedicated journal and dmcrypt enabled scenarios are failing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: z1
: 3.0
Assignee: Guillaume Abrioux
QA Contact: Vidushi Mishra
URL:
Whiteboard:
Depends On:
Blocks: 1536098
TreeView+ depends on / blocked
 
Reported: 2018-02-01 15:57 UTC by Ken Dreyer (Red Hat)
Modified: 2018-06-07 10:29 UTC (History)
15 users (show)

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:
Clone Of: 1536098
Environment:
Last Closed: 2018-03-08 15:52:40 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 2338 0 None None None 2018-02-01 15:57:42 UTC
Github ceph ceph-ansible pull 2339 0 None None None 2018-02-01 15:57:42 UTC
Red Hat Product Errata RHBA-2018:0474 0 normal SHIPPED_LIVE Red Hat Ceph Storage 3.0 bug fix update 2018-03-08 20:51:53 UTC

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


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