Comment 2 for bug 1456792

The fix needs to be added into the the lxc-system-manage tool which is used to bring the dnsmasq oinline for use within lxc

Master:
https://github.com/stackforge/os-ansible-deployment/blob/master/playbooks/roles/lxc_hosts/templates/lxc-system-manage.j2#L141-L158

The same thing can be done in Juno too:
https://github.com/stackforge/os-ansible-deployment/blob/juno/rpc_deployment/roles/lxc_common/files/lxc-system-manage#L134-L150

@Serge
As for the lxcbr0 interface, this is the device that all of the traffic leaving the lxc containers goes through. In master / Kilo this devices could be overriden and or changed using the `lxc_net_bridge` variable. There are several options available for setting up and defining the lxc network interface and will need to be configured for a successful deployment when using physical devices. These options can all be seen here: https://github.com/stackforge/os-ansible-deployment/blob/master/playbooks/roles/lxc_hosts/defaults/main.yml#L16-L31