Created attachment 1490208[details]
cephci_logs
Description of problem:
When executing the ceph-ansible playbook 'switch-from-non-containerized-to-containerized-ceph-daemons.yml', I am encountering the following fatal error:
2018-10-02 13:32:26,971 - ceph.ceph - INFO - fatal: [ceph-clacroix-1538508508439-node1-mon]: FAILED! => {"failed": true, "msg": "The
conditional check 'ceph_docker_image_tag | search(\"ubuntu\")' failed. The error was: Unexpected templating type error occurred on
({% if ceph_docker_image_tag | search(\"ubuntu\") %} True {% else %} False {% endif %}): expected string or buffer\n\nThe error appe
ars to have been in '/usr/share/ceph-ansible/switch-from-non-containerized-to-containerized-ceph-daemons.yml': line 76, column 7, bu
t may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n - name: set_fac
t ceph_uid for ubuntu\n ^ here\n"}
Version-Release number of selected component (if applicable):
ceph-ansible-3.1.5-1.el7cp.noarch
ceph version 12.2.5-42.el7cp (82d52d7efa6edec70f6a0fc306f40b89265535fb) luminous (stable)
How reproducible:
Steps to Reproduce:
1. Install ceph 3.1 using ceph-ansible
2. Ensure prereqs are met according to the doc: https://docs.google.com/document/d/1pV6BafagwoxTFgmi3UHcgqt5luH9X7tmZIogi1j4fXE
3. Run playbook: switch-from-non-containerized-to-containerized-ceph-daemons.yml
Actual results:
Failure due to the fatal message above.
Expected results:
Cluster successfully converted to containerized daemons.
Additional info:
The image tag looks to be non-quoted, so the error is likely caused by a python runtime error not expecting a numeric value (e.g. 3.1)
2018-10-03 10:45:31,360 - test_switch_to_containerized - INFO - gvar: {'ceph_docker_image': 'rhceph/rhceph-3-rhel7', 'ceph_docker_image_tag': 3.1, 'ceph_docker_registry': 'registry.access.redhat.com'}
Quoting the ceph_docker_image_tag value seems to have worked. After changing 3.1 to '3.1' the playbook executes successfully. I think converting the tag value to a string before searching is a good idea.
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-2019:0020