agentschedulers: concurrent port delete on unscheduling may cause unscheduling to fail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Kailun Qin |
Bug Description
When a network is removed from a dhcp agent, in some scenarios if the agent releases its port concurrently, there is chance that the removal of network from agent will fail due to that the target port is not found.
The issue can be reproduced on the latest devstack.
Steps to reproduce:
1. neutron port-list, identify the port to delete
2. Remove one network from a dhcp agent: neutron dhcp-agent-
AND at the same time delete the port associated: neutron port-delete xxx
Failed CLI:
vagrant@
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
Port 6089a77e-
Neutron server returns request_ids: ['req-dfecf6a3-
Failed Log:
DEBUG oslo.privsep.daemon [^[[00;36m-] ^[[01;35mprivsep: Exception during request[
Traceback (most recent call last):
File "/usr/local/
reply = self._process_
File "/usr/local/
ret = func(*f_args, **f_kwargs)
File "/usr/local/
return func(*args, **kwargs)
File "/opt/stack/
link = _run_iproute_
File "/opt/stack/
idx = _get_link_
File "/opt/stack/
raise NetworkInterfac
NetworkInterfac
Changed in neutron: | |
assignee: | nobody → Kailun Qin (kailun.qin) |
summary: |
- agentschedulers: concurrent port delete on unscheduling may cause port - not found + agentschedulers: concurrent port delete on unscheduling may cause + unscheduling to fail |
Changed in neutron: | |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. openstack. org/573097
Review: https:/