Description of problem:
ceph-ansible upstream just released 2.1.0 version. We need to resync the current ceph-ansible with this version.
QE needs to test and validate this new version, just like they did prior to release 2.1. If this is a success we can resync 2.1 during the next downstream resync.
Ken, could you please build the new package from https://github.com/ceph/ceph-ansible/releases/tag/v2.1.0
Version-Release number of selected component (if applicable):
Steps to Reproduce:
We will need v2.2.1 with https://github.com/ceph/ceph-ansible/pull/1217 cherry-picked.
Is this the final version of ceph-ansible that we will be using for 2.2?
(In reply to Tejas from comment #6)
> Is this the final version of ceph-ansible that we will be using for 2.2?
Yes, as of ceph-ansible v2.1.1.
...unless you find bugs and we have to ship newer versions.
Please make sure that updated package fix the following BZs which cause:
# error while evaluating conditional: raw_multi_journal and item.0.rc != 0
(In reply to Shinobu KINJO from comment #8)
> Please make sure that updated package fix the following BZs which cause:
> # error while evaluating conditional: raw_multi_journal and item.0.rc != 0
> * https://bugzilla.redhat.com/show_bug.cgi?id=1400967
> * https://bugzilla.redhat.com/show_bug.cgi?id=1405370
Ken, what is the plan on fixing above mentioned two bugs in 2.1.1?
To fix more issues (eg bug 1416010), we're going to update to ceph-ansible v2.1.4.
We uncovered additional bugs in v2.1.4, so we're going to ship v2.1.5
upstream's nightly ceph-installer integration tests uncovered an issue where ceph-installer breaks with ceph-ansible v2.1.5.
https://github.com/ceph/ceph-ansible/pull/1268 fixes this, and we are going to tag and build v2.1.6 with this change.
We landed more bug fixes (rhbz#1419814, rhbz#1418980) in v2.1.7, and we'll ship that version.
We have completed our testing of ceph-ansible with build :
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.