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: Low => 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/1226271

Title:
  VM state automatically transits from ERROR to ACTIVE

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Due to the periodic task "_check_instance_build_time," a VM is set
  from BUILD to ERROR because the related VM creation is delayed, for
  example, due to a temporary network partition. That VM can, however,
  transit from ERROR to ACTIVE, once the temporary partition is resolved
  and the VM creation completes.

  We found such an ERROR to ACTIVE transition problematic, in particular
  because it can happen without inputs/actions from an external user.
  The rationale is that, when a user tries to create a VM but finds that
  it is marked in an error state, the user will probably retry the VM
  creation. The above automatic state transition may thus give the user
  more VMs than he intends to create.

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