yahoo-eng-team team mailing list archive

[John Garbutt <john@xxxxxxxxxxxxxxx>]

Now instance actions has been implemented, lets kill this one, its more
of a feature really?

** Changed in: nova
       Status: Confirmed => Won't Fix

-- 
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/1061062

Title:
  Asynchronous errors can only be reported if instance is in ERROR

Status in OpenStack Compute (Nova):
  Won't Fix

Bug description:
  The API currently states that asynchronous errors can only be reported
  if the instance is in ERROR state. Nova currently implements that too.

  However, this implies that all problems that occur are fatal.

  One instance where an error may not necessarily be fatal is when
  communicating with the agent. During a spawn of a new instance, the
  agent is used (in the case of the xenapi driver at least) to set the
  root password, possibly inject files and set the network config.

  Often these problems leave the instance running, but maybe in a
  partially configured state. Moving the instance to ERROR should shut
  off the instance, leaving it unavailable to troubleshoot. Logging an
  asynchronous error doesn't make it visible to the user unless the
  instance is in ERROR.

  Right now the xenapi driver just logs agent failures and continues.
  This can leave the user confused as to why the instance doesn't appear
  to be configured correctly since there is no user accessible way to
  obtain non-fatal errors.

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