Description of problem: Encrypted OSD creation is failing when it is choosen to have dedicated journal devices. Version-Release number of selected component (if applicable): ceph version 10.2.3-12.el7cp ceph-ansible-1.0.5-39.el7scon.noarch How reproducible: Always Steps to Reproduce: 1. Install ceph-ansible 2. Change following settings in /usr/share/ceph-ansible/group_vars/osds file dmcrypt_dedicated_journal: true devices: - /dev/sdb raw_journal_devices: - /dev/sdd 3. Run playbook. Actual results: Expected results: Additional info: I have copied ansible-playbook log and group_vars folder to /home/ubuntu of magna111.ceph.redhat.com as 'ansible-log' and group_vars respectively.
I'm looking into this, I'm logged on the machines
Found the error, fix is already upstream. I need to cherry-pick that.
Andrew already fixed that here: https://github.com/ceph/ceph-ansible/pull/1060
Andrew is going to push that downstream today
I've got the necessary patches for this pushed downstream.
Ken, Could ypu please generate a downstream compose with this version of ceph-ansible: ceph-ansible-1.0.5-40.el7scon As its not there in the latest rhscon composes. Thanks, Tejas
Created attachment 1219213 [details] Recent log
Hi, Still it's failing. PLAY RECAP ******************************************************************** magna003 : ok=89 changed=0 unreachable=0 failed=0 magna013 : ok=89 changed=0 unreachable=0 failed=0 magna023 : ok=89 changed=0 unreachable=0 failed=0 magna056 : ok=202 changed=7 unreachable=0 failed=0 magna092 : ok=202 changed=7 unreachable=0 failed=0 magna112 : ok=202 changed=7 unreachable=0 failed=0 [ubuntu@magna003 ceph-ansible]$ sudo ceph -s cluster 3cdf8f83-bcb8-4051-9942-1ba7265ab0cf health HEALTH_ERR 64 pgs are stuck inactive for more than 300 seconds 64 pgs stuck inactive no osds monmap e1: 3 mons at {magna003=10.8.128.3:6789/0,magna013=10.8.128.13:6789/0,magna023=10.8.128.23:6789/0} election epoch 6, quorum 0,1,2 magna003,magna013,magna023 osdmap e1: 0 osds: 0 up, 0 in flags sortbitwise pgmap v2: 64 pgs, 1 pools, 0 bytes data, 0 objects 0 kB used, 0 kB / 0 kB avail 64 creating Moving back to ASSIGNED state. Regards, Vasishta
We test dmcrypt with dedicated journals with dmcrypt every day upstream now, and it works in the latest RPM (v2.1.9). I'm closing this as a dup of the general "dmcrypt support" bug, 1366808 *** This bug has been marked as a duplicate of bug 1366808 ***