yahoo-eng-team team mailing list archive

[Russell Bryant <1231890@xxxxxxxxxxxxxxxxxx>]

This is just the expected behavior of the nova API right now.

There is an active blueprint right now where we're adding the concept of
tasks to the API.  Hopefully this will give us a place in the API to
provide better details about which part of the process failed, and why.

** 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/1231890

Title:
  should report detail reason when passin invalid scheduler hint

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Using some special scheduler filter like SimpleCIDRAffinityFilter, JsonFilter.
  If user pass in a invalid CIDR string (Using SimpleCIDRAffinityFilter); or invalid json (Using JsonFilter).nova will return 202, then going to schedule the instance. But the instance will go to ERROR, which will confuse user. The only way to debug
  why instance is ERROR is that ask sysadmin to check log of nova-scheduler to find
  out what happened.

  I have two work around in head.

  1. Return 400(bad request) when user pass in a invalid scheduler-hint. Means we need to let nova-api know which filters the scheduler is using, and using the validator of these filters to validate user request.
  2. Still let instance going to ERROR, but expose a API to user to check the reason why the instance is ERROR.
  Now there is a API named 'action-list', but not include the fault information about the instance.

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