Public bug reported:
When a network is deleted, the port is deleted first and then the subnet
is deleted. When a port is deleted, neutron-dhcp-agent is notified. The
agent code goes to self.schedule_resync("Agent port was deleted",
port.network_id), which causes sync_state to be performed on the
network. If the subnet is not deleted, sync_state may deactivate DHCP.
In this case, DHCP port creation and subnet deletion are performed at
the same time, triggering deadlock.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2092983
Title:
deadlock： delete the network
Status in neutron:
New
Bug description:
When a network is deleted, the port is deleted first and then the
subnet is deleted. When a port is deleted, neutron-dhcp-agent is
notified. The agent code goes to self.schedule_resync("Agent port was
deleted", port.network_id), which causes sync_state to be performed on
the network. If the subnet is not deleted, sync_state may deactivate
DHCP. In this case, DHCP port creation and subnet deletion are
performed at the same time, triggering deadlock.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2092983/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
