5f46b70f80
The stacktrace observed seems to hint to a situation where a session is not properly rolled back when duplicate agent entries are found. Since it is ok to deal with duplicates, the addition of agents to the DB must be done one by one, otherwise we go against the ATOMICITY property of a transaction of all or none. It's either that or I am barking at the wrong tree. This patch also added UT to cover affected code. Closes-bug: 1282421 Related-bug: 1282253 Change-Id: Ic5f77808cc10f885d67f5a9cf3b3836283692850
# -- 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>.