yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Medium => Undecided

** Changed in: nova
       Status: Confirmed => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1072734

Title:
  Improve instance state recovery for Compute service failure during
  Create Server

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Scenario:

  Compute service spawns an instance but crashes just before instance's
  state is updated in database to Active, but instance has started
  running on the hypervisor.

  In this situation, the recovery of the instance requires admin
  intervention:

  - When compute service resumes, the check_instance_build_time periodic task sets the VM State to Error, while task state is still Spawning
  - To recover the instance, Admin now has to reset the instance's state to Active (task state gets reset to None)

  The instance can now be usable. The sync power state periodic task
  eventually sets the Power state to Running.

  However , this is a tedious workflow needing admin intervention and
  should be handled in the code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1072734/+subscriptions