Description of problem: Version-Release number of selected component (if applicable): oc v3.9.0-0.42.0 kubernetes v1.9.1+a0ce1bc657 features: Basic-Auth GSSAPI Kerberos SPNEGO How reproducible: always Steps to Reproduce: 1. install logging with openshift_logging_install_eventrouter=true 2. 3. Actual results: TASK [openshift_logging_eventrouter : Generate EventRouter template] *********** task path: /usr/share/ansible/openshift-ansible/roles/openshift_logging_eventrouter/tasks/install_eventrouter.yaml:24 Tuesday 13 February 2018 05:56:36 +0000 (0:00:00.354) 0:02:33.090 ****** fatal: [host-8-249-55.host.centralci.eng.rdu2.redhat.com]: FAILED! => {"changed": false, "msg": "Could not find or access '2.x/eventrouter-template.j2'\nSearched in:\n\t/usr/share/ansible/openshift-ansible/roles/openshift_logging_eventrouter/templates/2.x/eventrouter-template.j2\n\t/usr/share/ansible/openshift-ansible/roles/openshift_logging_eventrouter/2.x/eventrouter-template.j2\n\t/usr/share/ansible/openshift-ansible/roles/openshift_logging/templates/2.x/eventrouter-template.j2\n\t/usr/share/ansible/openshift-ansible/roles/openshift_logging/2.x/eventrouter-template.j2\n\t/usr/share/ansible/openshift-ansible/roles/openshift_logging_eventrouter/tasks/templates/2.x/eventrouter-template.j2\n\t/usr/share/ansible/openshift-ansible/roles/openshift_logging_eventrouter/tasks/2.x/eventrouter-template.j2\n\t/usr/share/ansible/openshift-ansible/playbooks/openshift-logging/private/templates/2.x/eventrouter-template.j2\n\t/usr/share/ansible/openshift-ansible/playbooks/openshift-logging/private/2.x/eventrouter-template.j2"} Expected results: Additional info: example inventory file [OSEv3:children] masters [masters] host-8-249-55.host.centralci.eng.rdu2.redhat.com openshift_public_hostname=host-8-249-55.host.centralci.eng.rdu2.redhat.com [etcd] host-8-249-55.host.centralci.eng.rdu2.redhat.com openshift_public_hostname=host-8-249-55.host.centralci.eng.rdu2.redhat.com [OSEv3:vars] ansible_ssh_user=root ansible_ssh_private_key_file="/tmp/tmp/libra.pem" deployment_type=openshift-enterprise # Logging openshift_logging_install_logging=true openshift_logging_kibana_hostname=logs.apps.0212-1r7.qe.rhcloud.com openshift_logging_kibana_ops_hostname=logs-ops.apps.0212-1r7.qe.rhcloud.com public_master_url=https://host-8-249-55.host.centralci.eng.rdu2.redhat.com:8443 openshift_logging_image_prefix=brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/ openshift_logging_image_version=v3.9 openshift_logging_namespace=vdxs5 # Extra_Logging openshift_logging_elasticsearch_cpu_limit=300m openshift_logging_elasticsearch_cpu_request=300m openshift_logging_elasticsearch_memory_limit=512Mi openshift_logging_es_cpu_limit=300m openshift_logging_es_cpu_request=300m openshift_logging_es_ops_cpu_limit=300m openshift_logging_es_ops_cpu_request=300m openshift_logging_es_memory_limit=512Mi openshift_logging_es_ops_memory_limit=512Mi openshift_logging_kibana_memory_limit=512Mi openshift_logging_kibana_ops_memory_limit=512Mi # request to use 1 dedicate CPU core openshift_logging_fluentd_cpu_request=1 openshift_logging_install_eventrouter=true # Metrics openshift_metrics_install_metrics=true openshift_metrics_hawkular_hostname=metrics.apps.0212-1r7.qe.rhcloud.com openshift_metrics_project=vdxs5 openshift_metrics_image_prefix=brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/ openshift_metrics_image_version=v3.9 # Extra_Metrics
ansible.noarch 2.4.2.0-2.el7
openshift-ansible branch id 1a9a61b
https://github.com/openshift/openshift-ansible/pull/7133
Tested with openshift-ansible-docs-3.9.0-0.47.0, event router pod could be in running status now. # rpm -qa | grep openshift-ansible openshift-ansible-docs-3.9.0-0.47.0.git.0.f8847bb.el7.noarch openshift-ansible-roles-3.9.0-0.47.0.git.0.f8847bb.el7.noarch openshift-ansible-3.9.0-0.47.0.git.0.f8847bb.el7.noarch openshift-ansible-playbooks-3.9.0-0.47.0.git.0.f8847bb.el7.noarch
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:0489