Present a better error message when the flavor creation fails

[Otavio Gaspareto]

When an error happens during the flavor creation thru the Horizon, the message "Unable to create flavor" is always presented to the user, without giving better directions on what caused the failure.

Would be more useful if the message had a more meaningful text. It could be reached presenting the error message sent from the backend exception that caused the failure.

[Henrique Truta (henriquetruta)]

Hello!

How can I reproduce this bug? I tried but was unable to do it...

[Nikunj Aggarwal (nikunj2512)]

Please can you explain how to reproduce this bug?

[Yamini Sardana (yamini-sardana)]

Steps to reproduce :
1. On the Flavors page, Click on Create Image
2. In the Name field, Specify the name of an existing image but in different case e.g m1.NANO
3. Enter other parameters and click on Create Flavor.
4. Error windows pop-up saying " Unable to create flavor <name>"

The error window does not specify the error due to which the image creation failed.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/266460
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=b5d27265542a143da9847cf87d9e9a24229b21f5
Submitter: Jenkins
Branch: master

commit b5d27265542a143da9847cf87d9e9a24229b21f5
Author: Lucas Palm <email address hidden>
Date: Tue Jan 12 10:12:58 2016 -0600

    Improve field validation/error handling for flavor creation

    Currently, if a user tries to create a new flavor or rename a flavor
    to a name that already exists, a field validation error will be shown
    that tells the user that the name is already being used by another
    flavor.

    It seems, however, that the validation does not catch the case where the
    user enters a flavor name that is the same string but just with
    uppercase/lowercase differences. Since this is not caught during the
    form validation, nova runs into an error later and thus throws an
    exception that leaves the user with a generic error message like
    "Unable to create flavor".

    To improve the form field validation and prevent the error from ever
    occurring in Nova, I switched the name comparisons to use the .lower()
    method. This was done for both Creating and Editing Flavor names.

    Change-Id: I44dcd98978e57282b44fdab8f134500eb9b03881
    Closes-Bug: #1179607

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/horizon 9.0.0.0b2 development milestone.