Created attachment 1322590 [details] File contains contents of inventory file and ansible-playbook log Description of problem: Restart ceph-defaults: retsceph mds task is failing on a node before configuring mdss. ceph-ansible was configured to colocate containerized osds with containerized mdss. While running ceph-defaults handlers after configuring osds, restart ceph mdss task failed as mds was not yet configured on the node. Same task was skipped on other nodes. But it should have skipped on this node also as mds was not yet configured. Version-Release number of selected component (if applicable): ceph-ansible-3.0.0-0.1.rc4.el7cp.noarch Steps to Reproduce: 1. Configure ceph-ansible to get a cluster with osds container colocated with mds. 2. Run ansible-playbook site-docker.yml Actual results: RUNNING HANDLER [ceph-defaults : restart ceph mdss] ********************************************************************************************** failed: [magna025 -> magna025] (item=magna025) => {"failed": true, "item": "magna025", "msg": "Could not find the requested service ceph-mds@magna025: host"} Expected results: restart ceph mdss must have been skipped before mds is configured Additional info: $ cat /etc/ansible/hosts -------- [osds] magna025 ------- [mdss] magna025
Created attachment 1322593 [details] File contains contents of inventory file and ansible-playbook log I had copied incorrect inventory file to the attachment, sincere apologies. Please consider this attachment for ansible-playbook log and inventory file. Regards, Vasishta
Created attachment 1322600 [details] File contains contents ansible-playbook log Same issue was seen with respect to rgw also. Ansible was configured to co-locate an OSD node and RGW node, while running handler ceph-defaults : restart ceph rgws on a node where osd was configured, it failed as RGW was not yet configured on the node. Regards, Vasishta
Hi Ken, ceph-ansible-3.0.0-0.1.rc7.el7cp is still not available for QE. It would be helpful if we can get this version of ceph-ansible soon for testing. Thanks, Vasishta
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