Remove ironic inspector dnsmasq bind-interfaces setting

In order to allow the ironic inspector dnsmasq service to
receive packets after the network service is restarted, the
bind-interfaces option should not be set.  Since the
ironic inspector is bound to the br-ctlplane interface,
its not necessary to set this field as this dnsmasq instance
will only service this interface.

From the dnsmasq man page (http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html).
-z, --bind-interfaces
On systems which support it, dnsmasq binds the wildcard address,
even when it is listening on only some interfaces. It then
discards requests that it shouldn't reply to. This has the
advantage of working even when interfaces come and go and
change address. This option forces dnsmasq to really bind only
the interfaces it is listening on. About the only time when
this is useful is when running another nameserver (or another
instance of dnsmasq) on the same machine. Setting this option
also enables multiple instances of dnsmasq which provide DHCP
service to run in the same machine.

We do run another dnsmasq instance for neutron but that is bound to
the tap interface in the namespace.

Change-Id: I88a0b67a61944565e59f245f02f7e4620f92ec82

releasenotes/notes/remove-bind-interfaces-98c7021ed271eeee.yaml

@@ -0,0 +1,25 @@
+---
+fixes:
+  - |
+    In order to allow the ironic inspector dnsmasq service to receive packets
+    after the network service is restarted, the bind-interfaces option should
+    not be set.  Since the ironic inspector is bound to the br-ctlplane
+    interface, its not necessary to set this field as this dnsmasq instance
+    will only service this interface.
+
+    From the `dnsmasq man page
+    <http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html>`_:
+
+        -z, --bind-interfaces
+        On systems which support it, dnsmasq binds the wildcard address, even
+        when it is listening on only some interfaces. It then discards requests
+        that it shouldn't reply to. This has the advantage of working even when
+        interfaces come and go and change address. This option forces dnsmasq
+        to really bind only the interfaces it is listening on. About the only
+        time when this is useful is when running another nameserver (or another
+        instance of dnsmasq) on the same machine. Setting this option also
+        enables multiple instances of dnsmasq which provide DHCP service to run
+        in the same machine.
+
+    We do run another dnsmasq instance for neutron but that is bound to the tap
+    interface in the namespace.

templates/inspector_dnsmasq_http.erb

@@ -1,6 +1,5 @@
 port=0
 interface=<%= @dnsmasq_interface %>
-bind-interfaces
 <% if @debug %>
 log-dhcp
 log-queries

templates/inspector_dnsmasq_tftp.erb

@@ -1,6 +1,5 @@
 port=0
 interface=<%= @dnsmasq_interface %>
-bind-interfaces
 <% if @debug %>
 log-dhcp
 log-queries