Hide Forgot
Description of problem: deploy logging failed using openshift-ansible:v3.7.22 Version-Release number of selected component (if applicable): openshift-ansible-3.7.22-1.git.0.a938a52.el7.noarch How reproducible: always Steps to Reproduce: 1.deploy logging 2. 3. Actual results: TASK [openshift_logging : include_role] **************************************** task path: /usr/share/ansible/openshift-ansible/roles/openshift_logging/tasks/install_logging.yaml:102 statically included: /usr/share/ansible/openshift-ansible/roles/openshift_logging_elasticsearch/tasks/determine_version.yaml ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path. The error appears to have been in '/usr/share/ansible/openshift-ansible/roles/openshift_logging_elasticsearch/handlers/main.yml': line 2, column 3, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: --- - name: "Restarting logging-{{ _cluster_component }} cluster" ^ here We could be wrong, but this one looks like it might be an issue with missing quotes. Always quote template expression brackets when they start a value. For instance: with_items: - {{ foo }} Should be written as: with_items: - "{{ foo }}" The error appears to have been in '/usr/share/ansible/openshift-ansible/roles/openshift_logging_elasticsearch/handlers/main.yml': line 2, column 3, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: --- - name: "Restarting logging-{{ _cluster_component }} cluster" ^ here We could be wrong, but this one looks like it might be an issue with missing quotes. Always quote template expression brackets when they start a value. For instance: Expected results: Additional info:
@Eric, Is this a change related to the restart logic you were recently working with? Is it something that was backported?
Can you please provide the full log output with -vvv verbosity? That error is misleading and doesn't seem to be indicative of what is actually going on. I remember seeing something like that when first testing this for master but resolved it, I believe it was due to the handler running twice for some reason which is why https://github.com/openshift/openshift-ansible/blob/a938a5208ae39b9d14879c07ada1922154645dcc/roles/openshift_logging_elasticsearch/handlers/main.yml#L11-L13 was added.
We believe this is resolved. Please retest with the version of openshift-ansible in #c3 or later
Tested with openshift-ansible-playbooks-3.7.23-1.git.0.bc406aa.el7.noarch, logging can be deployed successfully now.
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:0636