[Openstack-operators] [openstack-dev][openstack-operators][neutron[dhcp][dnsmask]: duplicate entries in addn_hosts causing no IP allocation
blak111 at gmail.com
Tue Jun 9 01:50:37 UTC 2015
I'm concerned that we are encountered out-of-order port events on the DHCP
agent side so the delete message is processed before the create message.
Would you be willing to apply a small patch to your dhcp agent to see if it
fixes the issue?
If it does fix the issue, you should see occasional warnings in the DHCP
agent log that show "Received message for port that was already deleted".
If it doesn't fix the issue, we may be losing the delete event entirely. If
that's the case, it would be great if you can enable debuging on the agent
and upload a log of a run when it happens.
Here is the patch:
diff --git a/neutron/agent/dhcp_agent.py b/neutron/agent/dhcp_agent.py
index 71c9709..9b9b637 100644
@@ -71,6 +71,7 @@ class DhcpAgent(manager.Manager):
self.needs_resync = False
self.conf = cfg.CONF
self.cache = NetworkCache()
+ self.deleted_ports = set()
self.root_helper = config.get_root_helper(self.conf)
ctx = context.get_admin_context_without_session()
@@ -151,6 +152,7 @@ class DhcpAgent(manager.Manager):
pool = eventlet.GreenPool(cfg.CONF.num_sync_threads)
known_network_ids = set(self.cache.get_network_ids())
+ self.deleted_ports = set()
active_networks = self.plugin_rpc.get_active_networks_info()
@@ -302,6 +304,10 @@ class DhcpAgent(manager.Manager):
def port_update_end(self, context, payload):
"""Handle the port.update.end notification event."""
+ if payload['port']['id'] in self.deleted_ports:
+ LOG.warning(_("Received message for port that was "
+ "already deleted: %s"), payload['port']['id'])
updated_port = dhcp.DictModel(payload['port'])
network = self.cache.get_network_by_id(updated_port.network_id)
@@ -315,6 +321,7 @@ class DhcpAgent(manager.Manager):
def port_delete_end(self, context, payload):
"""Handle the port.delete.end notification event."""
port = self.cache.get_port_by_id(payload['port_id'])
network = self.cache.get_network_by_id(port.network_id)
On Mon, Jun 8, 2015 at 8:26 AM, Daniel Comnea <comnea.dani at gmail.com> wrote:
> Any help, ideas please?
> On Mon, Jun 8, 2015 at 9:25 AM, Daniel Comnea <comnea.dani at gmail.com>
>> + Operators
>> Much thanks in advance,
>> On Sun, Jun 7, 2015 at 6:31 PM, Daniel Comnea <comnea.dani at gmail.com>
>>> Hi all,
>>> I'm running IceHouse (build using Fuel 5.1.1) on Ubuntu where dnsmask
>>> version 2.59-4.
>>> I have a very basic network layout where i have a private net which has
>>> 2 subnets
>>> 2fb7de9d-d6df-481f-acca-2f7860cffa60 | private-net
>>> | e79c3477-d3e5-471c-a728-8d881cf31bee 192.168.110.0/24
>>> | |
>>> f48c3223-8507-455c-9c13-8b727ea5f441 192.168.111.0/24 |
>>> and i'm creating VMs via HEAT.
>>> What is happening is that sometimes i get duplicated entries in  and
>>> because of that the VM which was spun up doesn't get an ip.
>>> The Dnsmask processes are running okay  and i can't see anything
>>> special/ wrong in it.
>>> Any idea why this is happening? Or are you aware of any bugs around this
>>> area? Do you see a problems with having 2 subnets mapped to 1 private-net?
>>> nobody 5664 1 0 Jun02 ? 00:00:08 dnsmasq --no-hosts
>>> --no-resolv --strict-order --bind-interfaces --interface=tapc9164734-0c
>>> --leasefile-ro --dhcp-authoritative
>>> --dhcp-range=set:tag1,192.168.111.0,static,86400s --dhcp-lease-max=512
>>> --conf-file= --server=10.0.0.31 --server=10.0.0.32 --domain=openstacklocal
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-operators