Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1217769 [details] ansible playbook log
I know where the bug is, it was introduced by a cherry pick of mine, in this commit: 3cd233fccda85126287558172b4d2548f9416fed to solve rhbz#1391468. Fix incoming.
I pushed a new commit: 473d5805f4bcdcc7e4327b14247c22fae1084fad in the rhscon-2-rhel-patches branch so Ken needs to build the package I guess.
Thanks Ken! Tejas please test and let me know :)
Created attachment 1218609 [details] ansible playbook log
Andrew, Alfredo, Ken: What do you guy think we should do here?
I think it should be best to drop it from this version. I don't feel confident in fixing this in time. I would like to prevent the situation where we add these fixes to either fail further or break other things that were working.
I've run ceph-ansible-1.0.5-41 through clot for RHEL and Ubuntu, so I know it passes the basic smoke tests for ceph-installer. On the other hand, we have no automated tests for the dmcrypt code paths. It's not clear what we'll uncover next w.r.t dmcrypt support at this point.
Spoke with Federico today, plan is: we'll see if Sebastien comes up with a fix by Wednesday and if that doesn't work we'll revert this, ship last known good version of ceph-ansible and use the process we documented for 2.0 here https://bugzilla.redhat.com/show_bug.cgi?id=1366808
I have attached the ansible playbook logs with -vvvv enabled just in case. Thanks, Tejas
Created attachment 1218850 [details] ansible playbook log with -vvvv
I just pushed a fix downstream. Ken please build a new package and Tejas please test. Thanks!
Created attachment 1219693 [details] ansible playbook log
Please ignore my comments no. 30, 31, 32. Those were meant for another BZ. Actually this BZ seems to be resolved in ceph-ansible-1.0.5-43.el7scon so Moving to verified.
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