Fixing dnsmasq container not starting bug

Two problems are fixed in this commit. Firstly handler
is not triggered so dnsmasq is not started. Secondly
dns is not working due to loop in dns settings.

Change-Id: If6874c99dcc42ef63da167abe8d1f7cdd8e0fcb1
Issue-ID: OOM-1866
Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>

diff --git a/ansible/roles/dns/handlers/main.yml b/ansible/roles/dns/handlers/main.yml
index 9e95747..cd1e4b4 100644 (file)
--- a/ansible/roles/dns/handlers/main.yml
+++ b/ansible/roles/dns/handlers/main.yml
@@ -3,7 +3,7 @@
   docker_container:
     name: dns-server
     image: "{{ dns_server_image }}"
-    command: -H /simulated_hosts --log-facility=-
+    command: -H /simulated_hosts --log-facility=- --dns-loop-detect
     capabilities: NET_ADMIN
     volumes:
       - "{{ app_data_path }}/cfg/simulated_hosts:/simulated_hosts:ro"

diff --git a/ansible/roles/dns/tasks/main.yml b/ansible/roles/dns/tasks/main.yml
index 121ee0c..8a7f8bc 100644 (file)
--- a/ansible/roles/dns/tasks/main.yml
+++ b/ansible/roles/dns/tasks/main.yml
@@ -26,3 +26,6 @@
   command: /bin/true
   notify: Run dns server container
   when: "'dns-server' not in containers_list.containers"
+
+- name: Force notified handlers to run at this point
+  meta: flush_handlers