[Octavia][osp16.1] Deploying Octavia with OctaviaLogOffload fails with error "Could not find or access templates/10-octavia.conf.j2" When deploying Octavia in Customized-Job [1] with the following OVERCLOUD_TEMPLATES parameters: tripleo_heat_templates: - /usr/share/openstack-tripleo-heat-templates/environments/services/octavia.yaml custom_templates: parameter_defaults: OctaviaLogOffload: true The job fails [2] in the Overcloud stage with the following error message: tl;dr: "Could not find or access 'templates/10-octavia.conf.j2'" Full message from overcloud_install.log: [controller-1]\nchanged: [controller-2]\n\nTASK [octavia-controller-post-config : create rsyslog 10-octavia.conf] *********\nWednesday 15 July 2020 11:48:45 -0400 (0:00:00.516) 0:02:48.245 ******** \nfatal: [controller-0]: FAILED! => {\"changed\": false, \"msg\": \"Could not find or access 'templates/10-octavia.conf.j2'\\nSearched in:\\n\\t/usr/share/ansible/roles/octavia-controller-post-config/templates/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/roles/octavia-controller-post-config/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/roles/octavia-controller-post-config/tasks/templates/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/roles/octavia-controller-post-config/tasks/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/tripleo-playbooks/templates/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/tripleo-playbooks/templates/10-octavia.conf.j2 on the Ansible Controller.\\nIf you are using a module and expect the file to exist on the remote, see the remote_src option\"}\nfatal: [controller-1]: FAILED! => {\"changed\": false, \"msg\": \"Could not find or access 'templates/10-octavia.conf.j2'\\nSearched in:\\n\\t/usr/share/ansible/roles/octavia-controller-post-config/templates/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/roles/octavia-controller-post-config/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/roles/octavia-controller-post-config/tasks/templates/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/roles/octavia-controller-post-config/tasks/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/tripleo-playbooks/templates/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/tripleo-playbooks/templates/10-octavia.conf.j2 on the Ansible Controller.\\nIf you are using a module and expect the file to exist on the remote, see the remote_src option\"}\nfatal: [controller-2]: FAILED! => {\"changed\": false, \"msg\": \"Could not find or access 'templates/10-octavia.conf.j2'\\nSearched in:\\n\\t/usr/share/ansible/roles/octavia-controller-post-config/templates/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/roles/octavia-controller-post-config/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/roles/octavia-controller-post-config/tasks/templates/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/roles/octavia-controller-post-config/tasks/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/tripleo-playbooks/templates/templates/10-octavia.conf.j2\\n\\t/usr/share/ansible/tripleo-playbooks/templates/10-octavia.conf.j2 on the Ansible Controller.\\nIf you are using a module and expect the file to exist on the remote, see the remote_src option\"}\n\nPLAY RECAP *********************************************************************\ncontroller-0 : ok=69 changed=37 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 \ncontroller-1 : ok=37 changed=15 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 \ncontroller-2 : ok=37 changed=15 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 \nundercloud-0 : ok=15 changed=6 unreachable=0 failed=0 skipped=15 rescued=0 ignored=0 \n\nWednesday 15 July 2020 11:48:45 -0400 (0:00:00.341) 0:02:48.587 ******** \n=============================================================================== I see that there is a bug upstream: https://bugs.launchpad.net/tripleo/+bug/1887516 [1] https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/OSPD-Customized-Deployment-virt/ [2] https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/OSPD-Customized-Deployment-virt/15996/
*** This bug has been marked as a duplicate of bug 1856835 ***