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:
upstream patch: https://github.com/ceph/ceph-ansible/pull/1527 backport: https://github.com/ceph/ceph-ansible/pull/1540 for now, let's just make sure this doesn't break anything, do not test FusionIO devices.
This BZ is does not describe the risks of not taking these fixes for RH Ceph Storage 2.3. Would you please fill out "Steps to Reproduce:", "Actual results:", and "Expected results:"? Without this information, it is not likely that the QE team will ack this bug.
None of our labs have fusionio devices :), but it nice to have those fio* drives detected. for the diff change, i believe not much can be done other than regression coverage.
Just released a new tag: https://github.com/ceph/ceph-ansible/releases/tag/v2.2.6. Can we get a new build?
Can we just make sure there is no regression with this and that's all?
I took this yesterday for regression run, its seems fine, so qa-ack, Its going to be useful where we have fio drives, not able to use those devices will be bad. but we should also add the ability to provide admin the option to choose drives via config items.
sanity 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-2017:1496