overLimit fault does not inform client of actual limit exceeded

[Brian Waldon]

Currently if you don't have enough resources to build an instance of a specific type, you get the following API response:

{"overLimit": {"message": "Instance quotas have been exceeded", "code": 413, "retryAfter": 0}}

This doesn't seem like enough information to be helpful to the user. I would love to see a better explanation of which quota was exceeded.

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/2221
Committed: http://github.com/openstack/nova/commit/8920181a0d8cfb4f78af0fa0b868e864d8971744
Submitter: Jenkins
Branch: master

 status fixcommitted
 done

commit 8920181a0d8cfb4f78af0fa0b868e864d8971744
Author: Brian Waldon <email address hidden>
Date: Fri Dec 9 11:16:04 2011 -0500

    Use more informative message when violating quota

    Fixes bug 902218

    Change-Id: I185ee726358876c074725f5297da5cedc761ec55

[David Naori (davidnaori3)]

Still getting uninformative error when exceeding cores limit:

ERROR: Quota exceeded: code=InstanceLimitExceeded (HTTP 413)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/8179

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/8179
Committed: http://github.com/openstack/nova/commit/84969afb3bfd467a2f48cf030a325c1a2fcd13ca
Submitter: Jenkins
Branch: master

commit 84969afb3bfd467a2f48cf030a325c1a2fcd13ca
Author: Pádraig Brady <email address hidden>
Date: Tue Jun 5 14:33:43 2012 +0100

    fix the instance quota overlimit message

    This addresses two closely related bugs.

    Bug: 998199
    Fix the "used" and "total" counts
    in the returned diagnostic.

    Bug: 902218
    Itemize instance quota items exceeded,
    in the returned diagnostic.

    Change-Id: Iff7781a7fb53545d44c2b4ec0ca6d65114723c8d