yahoo-eng-team team mailing list archive

[Lars Kellogg-Stedman <lars@xxxxxxxxxx>]

Public bug reported:

If you attempt to boot an image that is too large for a given flavor:

  $ nova boot --image fedora-21-cloud --flavor m1.tiny test0

The boot will of course fail, but the fault communicated to the client
is:

  | fault                                | {"message": "Build of
instance 05f6c907-61ed-4109-bc42-1c6cd1cfa663 aborted: Could not clean
up failed build, not rescheduling", "code": 500, "created":
"2015-03-28T18:49:55Z"} |

While in nova-compute.log is a more useful error:

  TRACE nova.compute.manager [instance:
05f6c907-61ed-4109-bc42-1c6cd1cfa663] FlavorDiskTooSmall: Flavor's disk
is too

It seems as if nova should provide this information in the "fault" key,
because it clearly communicates to someone attempting to boot an
instance why that instance failed to boot.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  FlavorDiskTooSmall exception should be communicated to client

Status in OpenStack Compute (Nova):
  New

Bug description:
  If you attempt to boot an image that is too large for a given flavor:

    $ nova boot --image fedora-21-cloud --flavor m1.tiny test0

  The boot will of course fail, but the fault communicated to the client
  is:

    | fault                                | {"message": "Build of
  instance 05f6c907-61ed-4109-bc42-1c6cd1cfa663 aborted: Could not clean
  up failed build, not rescheduling", "code": 500, "created":
  "2015-03-28T18:49:55Z"} |

  While in nova-compute.log is a more useful error:

    TRACE nova.compute.manager [instance:
  05f6c907-61ed-4109-bc42-1c6cd1cfa663] FlavorDiskTooSmall: Flavor's
  disk is too

  It seems as if nova should provide this information in the "fault"
  key, because it clearly communicates to someone attempting to boot an
  instance why that instance failed to boot.

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