yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #80569
[Bug 1850864] [NEW] DHCP agent takes very long time to report when port is provisioned
Public bug reported:
DHCP agent sends through rpc to neutron-server messages about ports which are already configured by agent: https://github.com/openstack/neutron/blob/3ad6af76266f466953de08451b922e033b5c8c43/neutron/agent/dhcp/agent.py#L255
It sends them in chunks with 64 ports at max.
Usually this works fine but in some cases when e.g. network with many ports (like 1000 for example) was resynced for some reason in "dhcp_ready_ports" there will be all those 1000 ports from resynced network.
And than new port may be at the end of this set and will be processed (send to neutron-server) after very long time. In our production cloud it could be even more than 15 minutes.
This cause problem with spawning vm which is in errors state due to "Failed to allocate network" error.
** Affects: neutron
Importance: Medium
Assignee: Slawek Kaplonski (slaweq)
Status: In Progress
** Tags: l3-ipam-dhcp
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1850864
Title:
DHCP agent takes very long time to report when port is provisioned
Status in neutron:
In Progress
Bug description:
DHCP agent sends through rpc to neutron-server messages about ports which are already configured by agent: https://github.com/openstack/neutron/blob/3ad6af76266f466953de08451b922e033b5c8c43/neutron/agent/dhcp/agent.py#L255
It sends them in chunks with 64 ports at max.
Usually this works fine but in some cases when e.g. network with many ports (like 1000 for example) was resynced for some reason in "dhcp_ready_ports" there will be all those 1000 ports from resynced network.
And than new port may be at the end of this set and will be processed (send to neutron-server) after very long time. In our production cloud it could be even more than 15 minutes.
This cause problem with spawning vm which is in errors state due to "Failed to allocate network" error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1850864/+subscriptions
Follow ups