yahoo-eng-team team mailing list archive

[Julien Vey <vey.julien@xxxxxxxxx>]

Public bug reported:

When trying to spawn a new instance on an OpenStack installation, and
the spawn fails with an error (for instance a driver error), you get a
message "No valid host was found." with an empty reason

It would help to have a more meaningful message when possible in order
to diagnose the problem

This would result for instance in having a message like

    Error: No valid host was found. Error from host: precise64 (node
precise64): InstanceDeployFailure: Image container format not supported
(ami) ].

instead of just (as it is currently)

    Error: No valid host was found.

** Affects: nova
     Importance: Undecided
     Assignee: Julien Vey (vey-julien)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Julien Vey (vey-julien)

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

Title:
  Improve error notification when schedule_run_instance fails

Status in OpenStack Compute (Nova):
  New

Bug description:
  When trying to spawn a new instance on an OpenStack installation, and
  the spawn fails with an error (for instance a driver error), you get a
  message "No valid host was found." with an empty reason

  It would help to have a more meaningful message when possible in order
  to diagnose the problem

  This would result for instance in having a message like

      Error: No valid host was found. Error from host: precise64 (node
  precise64): InstanceDeployFailure: Image container format not
  supported (ami) ].

  instead of just (as it is currently)

      Error: No valid host was found.

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