Description of problem: As we go into ceph 3.0 Luminous, we are mandatorily using RHEL 7.4. ceph-iscsi-ansible has a OS check for RHEL 7.3. This check should be set to RHEL 7.4. Version-Release number of selected component (if applicable): ceph-iscsi-ansible-1.5-5.el7scon.noarch.rpm
Fixed in the resync here: https://github.com/ceph/ceph-ansible/pull/1747
That PR isn't merged. Please move to POST once it is.
We can merge it upstream, however, we don't have any coverage upstream as we are waiting for CentIS 7.4 vagrant image.
(In reply to seb from comment #8) > We can merge it upstream, however, we don't have any coverage upstream as we > are waiting for CentIS 7.4 vagrant image. @Seb, when will this be done? Is there any other ways to speed up the delivery of fixed build to QE? As mentioned by Tejas earlier, this BZ is blocking our cpeh-iscsi-ansible testing. Please help.
Sorry Harish, I'll merge that today so QE can pursue its work
@Jason, I'll leave Ken answering that :)
@Ken, sure, I'm planning on tagging this morning.
(In reply to seb from comment #14) > @Ken, sure, I'm planning on tagging this morning. @Seb, can you please let us know when we will get the fix? This bug is actually blocking 6-7 days of test effort.
Tag is available, waiting for the package now :).
@Ken: should the ceph-ansible package now 'Obsoletes' the ceph-iscsi-ansible package?
Whoops, yes Jason.
https://github.com/ceph/ceph-ansible/pull/1899 adds the Obsoletes.
Can you send me the full output of "ansible harvard -m setup"?, thanks.
Created attachment 1327866 [details] ansible setup
Thanks, fix almost upstream.
Sébastien would you please tag and announce a new ceph-ansible version upstream with this change so we can rebase to it downstream?
I did, yesterday.
Verified in version ceph-ansible-3.0.0-0.1.rc10.el7cp
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:3387