Run of ceph-ansible-3.1.0-0.1.rc18.el7cp.noarch fails with the following: cat /var/lib/mistral/config-download-latest/ansible.log ... "fatal: [ceph-0]: FAILED! => {\"msg\": \"The conditional check 'ceph_release_num[ceph_stable_release] < ceph_release_num['luminous']' failed. The error was: error while evaluating conditional (ceph_release_num[ceph_stable_release] < ceph_release_num['luminous']): 'dict object' has no attribute u'dummy'\\n\\nThe error appears to have been in '/usr/share/ceph-ansible/roles/ceph-osd/tasks/openstack_config.yml': line 21, column 3, but may\\nbe elsewhere in the file depending on the exact syntax problem.\\n\\nThe offending line appears to be:\\n\\n\\n- name: set_fact rule_name before luminous\\n ^ here\\n\"}", "", "RUNNING HANDLER [ceph-defaults : set _mon_handler_called before restart] *******" ... 2018-08-20 06:32:21,418 p=1013 u=mistral | NO MORE HOSTS LEFT ************************************************************* 2018-08-20 06:32:21,419 p=1013 u=mistral | PLAY RECAP ********************************************************************* 2018-08-20 06:32:21,419 p=1013 u=mistral | ceph-0 : ok=99 changed=46 unreachable=0 failed=0 2018-08-20 06:32:21,419 p=1013 u=mistral | compute-0 : ok=117 changed=57 unreachable=0 failed=0 2018-08-20 06:32:21,419 p=1013 u=mistral | controller-0 : ok=157 changed=78 unreachable=0 failed=0 2018-08-20 06:32:21,419 p=1013 u=mistral | undercloud : ok=22 changed=11 unreachable=0 failed=1 2018-08-20 06:32:21,427 p=1013 u=mistral | Monday 20 August 2018 06:32:21 -0400 (0:03:05.474) 0:13:03.457 ********* 2018-08-20 06:32:21,428 p=1013 u=mistral | ============================================================================== Problem seems to be around Task "name: set_fact rule_name before luminous" from /usr/share/ceph-ansible/roles/ceph-osd/tasks/openstack_config.yml:21 . ceph-ansible-3.1.0-0.1.rc18.el7cp.noarch Output of ceph-ansible run: https://bugzilla.redhat.com/attachment.cgi?id=1477127
In https://github.com/ceph/ceph-ansible/releases/tag/v3.1.0rc19
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-2018:2819