Hi Logan,
Thanks for your quick answer and solution to the problem. I could do a
complete reinstall on this system so I did that and tried again with
your patch and it looks much better. Unbound is now deployed in
containers only and the bare metal machines are configured to use those
contain
Hi Andreas,
Thanks for reporting this. I just pushed a patch to resolve this here
https://review.openstack.org/#/c/431110/. If you are able to start
with a fresh environment this should resolve the issue. The unbound
service should only be installed in the containers, not the hosts, so
that was th
Hi!
I am using openstack-ansible 14.0.6-10 and have deployed Unbound but
there seems to be a conflict with Dnsmasq (that is installed by OSA) and
Unbound:
Feb 8 19:20:21 Infra8 unbound[5637]: [1486578021] unbound[6973:0]
error: can't bind socket: Address already in use for 0.0.0.0
Feb 8 19
