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 containers.

Regards,
Andreas


On 02/08/2017 08:05 PM, Logan V. wrote:
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 the issue here.

If you need to get this environment working where you saw this issue,
you could purge unbound from the hosts, apply the patch above, and
re-run the unbound-install playbook to refresh the resolv.conf across
the environment.

Logan

On Wed, Feb 8, 2017 at 12:45 PM, Andreas Vallin <[email protected]> wrote:
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:20:21 Infra8 unbound[5637]: [1486578021] unbound[6973:0] fatal
error: could not open ports

root@Infra8:~# netstat -pl|grep localhost:domain
tcp        0      0 localhost:domain *:*                     LISTEN
1840/dnsmasq
tcp6       0      0 localhost:domain [::]:*                  LISTEN
1840/dnsmasq
udp        0      0 localhost:domain *:*
1840/dnsmasq
udp6       0      0 localhost:domain [::]:*
1840/dnsmasq

Here is the config used in openstack_user_config.yml

unbound_hosts:
   Infra7:
     ip: 172.22.5.7
   Infra8:
     ip: 172.22.5.8
   Infra9:
     ip: 172.22.5.9

There are three containers created, one at each Infra machine (Unbound works
fine in the containers). Unbound also gets installed on the bare metal Infra
nodes and it is there the problem is. Is this a bug or something that I have
done wrong?

Regards,
Andreas


_______________________________________________
OpenStack-operators mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


_______________________________________________
OpenStack-operators mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to