Open Stack

Hi Lawrence,

Thanks for raising this.
The 10.255.255.x range is used by lxcbr0 on the host, to assign the eth0
address to the containers.
In essence this won't cause any issues - since we use the eth1 address
(which is statically configured) and we add the host entries to /etc/hosts.

That said, I see the logs you are mentioning, and whilst this won't cause
any issues I think we should look to resolve those logs if possible - I'll
create a bug for that.

https://bugs.launchpad.net/openstack-ansible/+bug/1668949

We do bug-triage once a week (on a Tuesday at 16:00 UTC) - so we'll
determine priority and if it's something worth fixing.

If you run into anymore issues or need help feel free to jump into
#openstack-ansible on Freenode, the channel is usually quite active, and
there are normally other deployers/operators or developers working with or
on OpenStack-Ansible who can help.

Thanks,
Andy


On 1 March 2017 at 10:51, Lawrence J. Albinson <lawrence at ljalbinson.com>
wrote:

> In the process of diagnosing an Ansible OpenStack multi-node build
> problem, I came across the following dnsmasq-dhcp errors in syslog.
>
> —— snip ——
> Feb 28 20:25:06 xh3 dnsmasq-dhcp[1956]: not giving name
> aio1-designate-container-f182826f to the DHCP lease of 10.255.255.226
> because the name exists in /etc/hosts with address 172.29.238.255
> Feb 28 20:25:06 xh3 dnsmasq-dhcp[1956]: not giving name
> aio1-swift-proxy-container-c298481d to the DHCP lease of 10.255.255.126
> because the name exists in /etc/hosts with address 172.29.237.136
> Feb 28 20:25:06 xh3 dnsmasq-dhcp[1956]: not giving name
> aio1-gnocchi-container-48fe5bde to the DHCP lease of 10.255.255.136
> because the name exists in /etc/hosts with address 172.29.239.156
> —— snip ——
>
> To simplify the situation, I built the All-in-One environment on a clean
> KVM-based Xenial 16.04.2 VM with a single non-DHCP NIC. The errors occur
> there too. This happens with both Ansible-OpenStack 15.0.0.0rc1 and 14.0.8.
>
> Are these errors a sign of misconfiguration on my part? Or are they a sign
> of a real problem or just noise?
>
> OpenStack itself would appear to be working.
>
> Kindest regards, Lawrence
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170301/4c68eaf8/attachment.html>