0dc730c7c0
Concurrent calls to _bind_port_if_needed may lead to a missing RPC notification which can cause a port stuck in a DOWN state. If the only caller that succeeds in the concurrency does not specify that an RPC notification is allowed then no RPC would be sent to the agent. The other caller which needs to send an RPC notification will fail since the resulting PortContext instance will not have any binding levels set. The failure has negative effects on consumers of the L2Population functionality because the L2Population mechanism driver will not be triggered to publish that a port is UP on a given compute node. Manual intervention is required in this case. This patch proposes to handle this by populating the PortContext with the current binding levels so that the caller can continue on and have an RPC notification sent out. Closes-Bug: #1755810 Story: 2003922 Change-Id: Ie2b813b2bdf181fb3c24743dbd13487ace6ee76a |
||
---|---|---|
api-ref | ||
bin | ||
devstack | ||
doc | ||
etc | ||
neutron | ||
playbooks | ||
rally-jobs | ||
releasenotes | ||
roles | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.pylintrc | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
TESTING.rst | ||
babel.cfg | ||
bindep.txt | ||
lower-constraints.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
Welcome!
To learn more about neutron:
- Documentation: https://docs.openstack.org
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
- Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
Get in touch via email. Use [Neutron] in your subject.
To learn how to contribute:
CONTRIBUTING.rst