Description of problem: Deploy logging by using ansible, it threw an error, the message is: RUNNING HANDLER [openshift_logging_elasticsearch : assert] ********************* Tuesday 22 May 2018 03:04:21 +0000 (0:00:00.028) 0:06:32.085 *********** fatal: [$master-url]: FAILED! => {"failed": true, "msg": "The conditional check 'not _pod_status.failed' failed. The error was: error while evaluating conditional (not _pod_status.failed): 'dict object' has no attribute 'failed'"} But after running ansible-playbook, all pods in openshift-logging are running. # oc get pod -n openshift-logging NAME READY STATUS RESTARTS AGE logging-curator-1-9c8x4 1/1 Running 0 25m logging-es-data-master-zx7zarh1-1-4rcj8 2/2 Running 0 24m logging-fluentd-65j5x 1/1 Running 0 24m logging-fluentd-wxjqf 1/1 Running 0 24m logging-kibana-1-9pw2j 2/2 Running 0 26m Version-Release number of selected component (if applicable): openshift v3.10.0-0.50.0 kubernetes v1.10.0+b81c8f8 openshift-ansible-3.10.0-0.50.0.git.0.bd68ade.el7.noarch logging-curator-v3.10.0-0.50.0.0 logging-elasticsearch-v3.10.0-0.50.0.0 logging-fluentd-v3.10.0-0.50.0.0 How reproducible: Always Steps to Reproduce: 1.Deploy logging, set openshift_logging_install_logging=true in inventory and run ansible-playbook 2. 3. Actual results: The ansible-playbook failed Expected results: Asible-playbook could run successfully without any error. Additional info:
https://github.com/openshift/openshift-ansible/pull/8466
Verified on openshift v3.10.0-0.53.0.
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:1816