f75054f595
Initially the symptom looks like race condition between two threads when stopping the task manager. After further analysis/troubleshooting, it turns out that two threads are spawned if a task manager is stopped and started again, causing unexpected errors. The IF check on the spawned thread sometimes return True sometime return False if not compared against None explicitly. This makes start() method think no thread has been started or stop() method think no thread is started. Change the check to compare against None. Also fixed a problem in unit-test where a thread may never terminated when a stop call is invoked during db access. Closes-Bug: 1221486 Change-Id: I0d67bfe8fef7a390f0d6bc0f5a42835f86a9fb27
# -- 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>.