76ee64f4a8
There is a python-ovs bug that allows transactions to be executed before it has started monitoring the db for changes. This breaks ovsdbapp's AddCommand behavior, which looks up a row in memory post-commit to return it to the caller, because we process the reply from ovsdb-server that has the UUID in it, but when we try to look it up in memory, it isn't there since that is handled via the monitor notifications. Since we don't care about the return value, we can just ignore the KeyError. In addition, the request to Idl.cond_change() to monitor only the neutron_pg_drop table was failing for a similar reason-- it is called before the initial monitor request is sent, so directly setting table.condition will allow the condition to be added to the initial monitor request. Closes-Bug: #1938766 Change-Id: I78af15970a86923fb810e903d38634b6e60a8fe4 |
||
---|---|---|
api-ref | ||
devstack | ||
doc | ||
etc | ||
neutron | ||
playbooks | ||
rally-jobs | ||
releasenotes | ||
roles | ||
tools | ||
vagrant/ovn | ||
zuul.d | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.pylintrc | ||
.stestr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
TESTING.rst | ||
bindep.txt | ||
lower-constraints.txt | ||
plugin.spec | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
OpenStack Neutron
Neutron is an OpenStack project to provide "network connectivity as a service" between interface devices (e.g., vNICs) managed by other OpenStack services (e.g., Nova).
To learn more about neutron:
- Documentation: https://docs.openstack.org/neutron/latest/
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
- Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
- Source: https://opendev.org/openstack/neutron
Get in touch via email. Use [Neutron] in your subject.
To learn how to contribute, please read the CONTRIBUTING.rst file.