Server resize error message indicates field which does not match request

[Brad Pokorny]

With a post of this resize body to the nova API, "ram" is specified:

Body :

{"resize":{"flavor":{"vcpus":1,"ram":9999999999,"disk":20,"extra_specs":{"key:smt":"-1"}}}}

The response refers to the same field as "memory_mb":

Response :

{
badRequest: {
message: "Invalid input received: memory_mb must be <= 2147483647"
code: 400
}-

It would seem to make more sense if the response referred to the same field as the request.

[Matt Riedemann (mriedem)]

The error is coming from checking the instance_type db fields I think, so that's what you're getting back in the error message. The flavors util doing the validation would have to map the api fields to the db fields if you wanted to cleanup the error message.

[Christopher Yeoh (cyeoh-0)]

What release of Nova are you running against? I don't think that is a valid body request in the first place (even without the ram issue) as it takes a flavorRef as the resize parameter.

http://docs.openstack.org/api/openstack-compute/2/content/POST_resizeServer__v2__tenant_id__servers__server_id__action_Server_Actions-d1e3229.html#POST_resizeServer__v2__tenant_id__servers__server_id__action_Server_Actions-d1e3229-Request

[Sean Dague (sdague)]

I think this is using an out of tree extension

[Matt Riedemann (mriedem)]

The root issue reported here was addressed in bug 1350751 and this change:

https://review.openstack.org/#/c/110891/

Basically make the error message that the user sees have the same fields that are in the API request rather than the DB model fields.