yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

This isn't a bug. This is an opinion at best. Depending on where and how
the instance fails, an instance fault might be record which, by default
policy rules, an administrator can see when getting instance details
from the REST API. But exposing the internals of why something failed to
the non-admin end user of the cloud, like that mysql is down, is not
something we're going to do.

** Changed in: nova
       Status: New => Invalid

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

Title:
  Wrong error messege in CreateInstance

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  In createInstance usecase execution, when we stop mysqld service and
  try to create an instance using command "nova boot --flavor <FLAVOR-
  ID> --image <NAME> --nic net-id=<NET-ID> --security-group <security-
  groups> --key-name <key-name> <name>". The instance is not created and
  generates an "InternalServerError". User must be informed about the
  proper cause of the problem with specific error message instead of
  InternalServerError which is generic error message.

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