David McNally cc0be157d0 Recover from REBOOT-* state on compute manager start-up ... If a compute manager is stopped / fails during certain REBOOT-* operations then the instance will be left stuck in a transitional task_state This change handles two possible task states REBOOT_PENDING and REBOOT_STARTED (for both soft and hard reboots). And either clears these states or retries the reboot depending on the instance state. Both task states are set after the request has gotten to the compute manager so we can handle these safely knowing the operation has ended/failed with the restart of the compute manager. We retry the reboot where the state is PENDING and where the state is STARTED and the instance is not running. Where the instance is running and the state is STARTED we simply transition the instance to an ACTIVE state. The user can retry the reboot if required. Related to blueprint recover-stuck-state Change-Id: Ib318b3d444a67616441302f3daa8de20ee946f3f		2014-03-12 10:00:54 +00:00
..
ec2	Task cleanup_running_deleted_instances can now use slave	2014-03-10 12:37:13 -06:00
openstack	Recover from REBOOT-* state on compute manager start-up	2014-03-12 10:00:54 +00:00
__init__.py	Remove vi modelines	2014-02-03 14:19:44 +00:00
test_auth.py	Remove middleware ratelimits from v3 api	2013-12-15 18:52:03 +08:00
test_sizelimit.py	Replace assertEquals with assertEqual - tests/api	2013-10-31 02:23:46 +09:00
test_validator.py	Remove @author from copyright statements.	2014-02-12 05:17:10 +11:00
test_wsgi.py	Remove vi modelines	2014-02-03 14:19:44 +00:00