12b9149e20
When the L3 agent get a router update notification, it will try to retrieve the router info from neutron server. But at this time, if the message queue is down/unreachable. It will get exceptions related message queue. The resync actions will be run then. Sometimes, rabbitMQ cluster is not so much easy to recover. Then Long time MQ recover time will cause the router info sync RPC never get successful until it meets the max retry time. Then the bad thing happens, L3 agent is trying to remove the router now. It basically shutdown all the existing L3 traffic of this router. This patch directly removes the final router removal action, let the router run as it is. Closes-Bug: #1871850 Change-Id: I9062638366b45a7a930f31185cd6e23901a43957 |
||
|---|---|---|
| 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 | ||
| babel.cfg | ||
| 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.