dnsmasq-dhcp log spam from lxbr0

[Andy McCrae]

If you look in /var/log/daemon.log there is spam about DHCP due to /etc/hosts entries:

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

This happens on an aio1 and doesn't impact the running of the system but seems like we may be able to avoid these logs.

[Viggo Ahl (viah01)]

I got this in the log when I install the OS with openstack-ansible.
Which halted the
TASK [lxc_container_create : Wait for ssh to be available]

It seems that the containers first is giving one ip-nummer that then is faulty. Because this ip-number is not reachable for the system.

ay 18 10:34:54 osansible dnsmasq-dhcp[20844]: not giving name infra1_nova_console_container-a0de8881 to the DHCP lease of 10.0.3.19 because the name exists in /etc/hosts with address 10.0.2.137
May 18 10:34:54 osansible dnsmasq-dhcp[20844]: not giving name infra1_nova_conductor_container-56d0c1ae to the DHCP lease of 10.0.3.126 because the name exists in /etc/hosts with address 10.0.3.105
May 18 10:34:54 osansible dnsmasq-dhcp[20844]: not giving name infra1_nova_api_metadata_container-cecfd7af to the DHCP lease of 10.0.3.210 because the name exists in /etc/hosts with address 10.0.0.209
May 18 10:34:54 osansible dnsmasq-dhcp[20844]: not giving name infra1_nova_api_os_compute_container-62476f7e to the DHCP lease of 10.0.3.208 because the name exists in /etc/hosts with address 10.0.0.204
May 18 10:34:54 osansible dnsmasq-dhcp[20844]: not giving name infra1_nova_api_placement_container-57c76c43 to the DHCP lease of 10.0.3.3 because the name exists in /etc/hosts with address 10.0.1.34
May 18 10:34:54 osansible dnsmasq-dhcp[20844]: not giving name infra1_horizon_container-ddddad42 to the DHCP lease of 10.0.3.225 because the name exists in /etc/hosts with address 10.0.3.48
May 18 10:34:54 osansible dnsmasq-dhcp[20844]: not giving name infra1_keystone_container-e299b0e8 to the DHCP lease of 10.0.3.241 because the name exists in /etc/hosts with address 10.0.3.227
May 18 10:34:54 osansible dnsmasq-dhcp[20844]: not giving name infra1_nova_scheduler_container-e9216f47 to the DHCP lease of 10.0.3.97 because the name exists in /etc/hosts with address 10.0.0.36
May 18 10:34:54 osansible dnsmasq-dhcp[20844]: not giving name infra1_neutron_server_container-3dc17aff to the DHCP lease of 10.0.3.184 because the name exists in /etc/hosts with address 10.0.1.152
May 18 10:34:54 osansible dnsmasq-dhcp[20844]: not giving name infra1_neutron_agents_container-65aab27a to the DHCP lease of 10.0.3.193 because the name exists in /etc/hosts with address 10.0.0.124
May 18 10:34:54 osansible dnsmasq-dhcp[20844]: not giving name infra1_glance_container-bd2428de to the DHCP lease of 10.0.3.219 because the name exists in /etc/hosts with address 10.0.3.24

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/494675

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/494675
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-lxc_hosts/commit/?id=2ffcc79451491b038389398e68d0cc4578d5d4df
Submitter: Jenkins
Branch: master

commit 2ffcc79451491b038389398e68d0cc4578d5d4df
Author: Major Hayden <email address hidden>
Date: Thu Aug 17 13:46:16 2017 -0500

    Prevent dnsmasq from reading hosts file

    OpenStack-Ansible configures /etc/hosts with the management IP
    addresses of containers, but dnsmasq gets confused when it sees those
    host names associated with a 10.X address on the lxc bridge. It
    causes lots of errors in the log files like these:

      not giving name hydrogen_rsyslog_container-307df194 to the DHCP
      lease of 10.0.3.196 because the name exists in /etc/hosts with
      address 172.29.239.71

    This patch adds the --no-hosts option for dnsmasq so that it will
    stop reading /etc/hosts and filling up log files.

    Closes-Bug: 1668949
    Change-Id: I7aa2f0081d7d79ab42fcfc28e3ed6839a4f66c8a

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/496261

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/496262

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/496263

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/496261
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-lxc_hosts/commit/?id=16ed92a02d6225c18172ac8b2d23e2e3efdb8718
Submitter: Jenkins
Branch: stable/pike

commit 16ed92a02d6225c18172ac8b2d23e2e3efdb8718
Author: Major Hayden <email address hidden>
Date: Thu Aug 17 13:46:16 2017 -0500

    Prevent dnsmasq from reading hosts file

    OpenStack-Ansible configures /etc/hosts with the management IP
    addresses of containers, but dnsmasq gets confused when it sees those
    host names associated with a 10.X address on the lxc bridge. It
    causes lots of errors in the log files like these:

      not giving name hydrogen_rsyslog_container-307df194 to the DHCP
      lease of 10.0.3.196 because the name exists in /etc/hosts with
      address 172.29.239.71

    This patch adds the --no-hosts option for dnsmasq so that it will
    stop reading /etc/hosts and filling up log files.

    Closes-Bug: 1668949
    Change-Id: I7aa2f0081d7d79ab42fcfc28e3ed6839a4f66c8a
    (cherry picked from commit 2ffcc79451491b038389398e68d0cc4578d5d4df)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/496262
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-lxc_hosts/commit/?id=412884fd9d803f1df2f4fc53b9c382ae606db67f
Submitter: Jenkins
Branch: stable/ocata

commit 412884fd9d803f1df2f4fc53b9c382ae606db67f
Author: Major Hayden <email address hidden>
Date: Thu Aug 17 13:46:16 2017 -0500

    Prevent dnsmasq from reading hosts file

    OpenStack-Ansible configures /etc/hosts with the management IP
    addresses of containers, but dnsmasq gets confused when it sees those
    host names associated with a 10.X address on the lxc bridge. It
    causes lots of errors in the log files like these:

      not giving name hydrogen_rsyslog_container-307df194 to the DHCP
      lease of 10.0.3.196 because the name exists in /etc/hosts with
      address 172.29.239.71

    This patch adds the --no-hosts option for dnsmasq so that it will
    stop reading /etc/hosts and filling up log files.

    Closes-Bug: 1668949
    Change-Id: I7aa2f0081d7d79ab42fcfc28e3ed6839a4f66c8a
    (cherry picked from commit 2ffcc79451491b038389398e68d0cc4578d5d4df)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/496263
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-lxc_hosts/commit/?id=dad3bd51306ac68fb622eae45bccf1e20a631f82
Submitter: Jenkins
Branch: stable/newton

commit dad3bd51306ac68fb622eae45bccf1e20a631f82
Author: Major Hayden <email address hidden>
Date: Thu Aug 17 13:46:16 2017 -0500

    Prevent dnsmasq from reading hosts file

    OpenStack-Ansible configures /etc/hosts with the management IP
    addresses of containers, but dnsmasq gets confused when it sees those
    host names associated with a 10.X address on the lxc bridge. It
    causes lots of errors in the log files like these:

      not giving name hydrogen_rsyslog_container-307df194 to the DHCP
      lease of 10.0.3.196 because the name exists in /etc/hosts with
      address 172.29.239.71

    This patch adds the --no-hosts option for dnsmasq so that it will
    stop reading /etc/hosts and filling up log files.

    Closes-Bug: 1668949
    Change-Id: I7aa2f0081d7d79ab42fcfc28e3ed6839a4f66c8a
    (cherry picked from commit 2ffcc79451491b038389398e68d0cc4578d5d4df)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-lxc_hosts 16.0.0.0rc2 release candidate.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-lxc_hosts 14.2.9 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-lxc_hosts 15.1.9 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-lxc_hosts 17.0.0.0b1 development milestone.