Creating extra capabilities with keys longer than 64 characters triggers an Internal Server Error

[Pierre Riteau]

Because the database field is limited to 64 characters, creating hosts with longer keys throws an exception which results in "ERROR: Internal Server Error" being displayed to users. The host is still created though, but without the capability.

We should return a 400 Bad Request error instead, and probably not create the host at all.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/575699
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=580d4ae470520e6c72f34b11943dec475d0af8e9
Submitter: Zuul
Branch: master

commit 580d4ae470520e6c72f34b11943dec475d0af8e9
Author: Masahito Muroi <email address hidden>
Date: Fri Jun 15 18:12:21 2018 +0900

    Return 400 Bad Request for extra capability keys longer than 64 chars

    Length of extra capability keys is limited to 64 characters in the DB
    schema. However, the host create API can create a host based on a
    request that has a longer extra capability key, only to return a 500
    Internal Server Error.

    With this patch, the API checks the key length before creating a host
    and returns a 400 Bad Request status code if it is too long.

    Change-Id: I2cf4ede787e0f65385376832ce410d694df094ff
    Closes-Bug: #1709639

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/blazar 2.0.0.0b3 development milestone.