b78eea6146
If the dhcp-agent machine restarts when openvswitch comes up it logs the following warning messages for all tap interfaces that do not exist: bridge|WARN|could not open network device tap2cf7dbad-9d (No such device) Once the dhcp-agent starts it recreates the interfaces and re-adds them to the ovs-bridge. Unfortunately, ovs does not reinitialize the interfaces as they are already in ovsdb and does not assign them a ofport number. This situation corrects itself though the next time a port is added to the ovs-bridge which is why no one has probably noticed this issue till now. In order to correct this we should first remove interface that exist and then readd them. Closes-bug: #1268762 Change-Id: I4bb0019135ab7fa7cdfa6d5db3bff6eafe22fc85
# -- 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>.