If internal_network_added/removed fails, _sync_routers_task will call process_router to do fault recovery. Because the port is already added/removed to/from ri.internal_ports, internal_network_added or internal_network_removed will not be called again. The patch fix this issue by calling ri.internal_ports.append/removed only if internal_network_added/removed succeed. Without the patch, the added testcases would fail. Change-Id: I2d2e004caa670c1624257c1d7ccc900438b42d08 Co-Authored-By: Hirofumi Ichihara <ichihara.hirofumi@lab.ntt.co.jp> Closes-Bug: #1255871
# -- Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
# -- External Resources:
The homepage for Neutron is: http://launchpad.net/neutron . Use this site for asking for help, and filing bugs. Code is available on github at <http://github.com/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
Neutron Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/
Neutron API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/
The start of some developer documentation is available at: http://wiki.openstack.org/NeutronDevelopment
For help using or hacking on Neutron, you can send mail to <mailto:openstack-dev@lists.openstack.org>.