Looks like not using a non-standard cluster name is the issue. I have updated the config modules on each of the gateways to pass the relevant conf file, which allows the rbd's to be created - but the playbook still fails msg: Could not find dm multipath device for ansible1 trying to run multipath -ll on a gateway shows there is a problem in the dm layer (maybe ceph.conf is hard-coded?) Last login: Tue Oct 25 04:50:58 2016 from magna006.ceph.redhat.com [root@magna058 ~]# multipath -ll Oct 25 04:52:19 | rbd0: Could not read rados conf Oct 25 04:52:19 | rbd1: Could not read rados conf Oct 25 04:52:19 | rbd2: Could not read rados conf I can patch the lun.py module so in the next code drop the rbd interaction is ok - however, I need Mike to look at the multipath settings
The multipath part of the fix will be done in bz https://bugzilla.redhat.com/show_bug.cgi?id=1388557
brew builds that address the original issue of files not being copied correctly are here http://download.eng.bos.redhat.com/brewroot/packages/ceph-iscsi-config/1.4/1.el7cp/noarch/ceph-iscsi-config-1.4-1.el7cp.noarch.rpm http://download.eng.bos.redhat.com/brewroot/packages/ceph-iscsi-ansible/1.4/1.el7scon/noarch/ceph-iscsi-ansible-1.4-1.el7scon.noarch.rpm
Verified in build: ceph-iscsi-ansible-1.5-1.el7test.noarch ceph-iscsi-config-1.5-1.el7test.noarch
While this is fixed in the ceph-iscsi-config-1.4-1/ceph-iscsi-config-1.4-1 RPMs, it is dependent upon an associated change in multipath-tools.
Verified in build: ceph-iscsi-config-1.5-1
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