# Revision history [back]

Hey guys @dbaxps @jkilborn I am facing the same issue in my environment , I have to the point same issue , whenever I restart the neutron-dhcp-agent.service it updates the dnsmasq hosts file from database and all new VMs get the IP.

The funny part with my environment is that this is only happening very randomly , so like I have 120 namespaces and among this randomly any 2 or 3 tenant network has this issue. I am just not sure what the issue is neutron-dhcp-agent is not able to do that and just give away this. any pointers would be appreciated.

I have controller which hosts API services and Neutron server on separate node and multiple compute nodes. Please help.

"DHCPDISCOVER(tapXXX) fa:16:3e:ec:bd:ad "no address available" dnsmasq-dhcp[3633]: 3621066038 available DHCP subnet: 172.17.x.x/255.255.255.0


Hey guys @dbaxps @jkilborn I am facing the same issue in my environment , I have to the point same issue , whenever I restart the neutron-dhcp-agent.service it updates the dnsmasq hosts file from database and all new VMs get the IP.

The funny part with my environment is that this is only happening very randomly , so like I have 120 namespaces and among this very randomly any 1 or 2 or 3 tenant network has this issue. reports this issue nad it's not always the same tenant it's very random. I am just not sure what the issue is neutron-dhcp-agent is not able to do that and just give away this. any pointers would be appreciated.

I am aware of the fact that once neutron creates the port , dhcp agent which is talking to database has to update it's namespace files/records , but I am just not sure why randomly someday this doesn't happen for 1 or 2 tenant network.

I have controller which hosts API services and Neutron server on separate node and multiple compute nodes. Please help.

"DHCPDISCOVER(tapXXX) fa:16:3e:ec:bd:ad "no address available" dnsmasq-dhcp[3633]: 3621066038 available DHCP subnet: 172.17.x.x/255.255.255.0


Hey guys @dbaxps @jkilborn I am facing the same issue in my environment , I have to the point same issue , whenever I restart the neutron-dhcp-agent.service it updates the dnsmasq hosts file from database and all new VMs get the IP.

The funny part with my environment is that this is only happening very randomly , so like I have 120 namespaces and among this very randomly any 1 or 2 tenant network reports this issue nad it's not always the same tenant it's very random. I am just not sure what the issue is neutron-dhcp-agent is not able to do that and just give away this. any pointers would be appreciated.

I am aware of the fact that once neutron creates the port , dhcp agent which is talking to database has to update it's namespace files/records , but I am just not sure why randomly someday this doesn't happen for 1 or 2 tenant network.

I have controller which hosts API services and Neutron server on separate node and multiple compute nodes. Please help.

"DHCPDISCOVER(tapXXX) fa:16:3e:ec:bd:ad "no address available" dnsmasq-dhcp[3633]: 3621066038 available DHCP subnet: 172.17.x.x/255.255.255.0


Also every time when I bounce the neutron-dhcp-agent service it reloads the files in dhcp namespace and all works fine. It also happened with me that when I tried to bounce the neutron-dhcp-agent service it also rebooted the neutron server itself.