error messages when failing floating IP association are too specific and too generic

[Matthew D. Wood]

When trying to associate a 2nd floating IP to an instance, to error messages are displayed.

One error message is the neutron/quantum message, which isn't really suitable for a normal user. The second is a very generic "Unable to associate IP..." message.

This should be cleaned up and a more informative message should be given to the user.

[Akihiro Motoki (amotoki)]

There are several things to do.
In Horizon side, we need to make sure only one message is displayed and
and it is better to contain possible error reason in the message.

Ideally it is better to improve neutron error message for more user friendly one.
There is a general discussion on improving user visible message in API.
Until then, Horizon needs to translate error messages :(

[Akihiro Motoki (amotoki)]

For better error message. the related blueprint is https://blueprints.launchpad.net/horizon/+spec/improve-error-message-details-for-usability

[Akihiro Motoki (amotoki)]

The main issue is being tracked in bug 1301374.

I would like to use this bug to track useless error message and still keep this bug open.

> One error message is the neutron/quantum message, which isn't really suitable for a normal user. The second is a very generic "Unable to associate IP..." message.

[Julie Pichon (jpichon)]

Akihiro, what you suggest makes sense to me. The title/description for this bug should probably be updated then.

[Cindy Lu (clu-m)]

Related bug: https://bugs.launchpad.net/horizon/+bug/1278353

[Akihiro Motoki (amotoki)]

After investigating Neutron Floating IP behavior, it looks good if we can handle 409 Conflict error.
When 409 is returned, Floating IP association logic in Horizon should raise the following message:

  The requested instnace port is already associated with another floating IP.

The fix highly depends on bug 1301374, so I will wait for the progress of the bug.

[Akihiro Motoki (amotoki)]

The fix itself is http://paste.openstack.org/show/97831/
I will wait for the fix of workflow itself.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit debd142fb27337ff2debd2224b8a48256693618c
Author: Vlad Okhrimenko <email address hidden>
Date: Wed Nov 5 15:37:15 2014 +0200

    Error messages for failing floating IP association

    Add more informative error message when trying to
    associate a 2nd floating IP to an instance

    Change-Id: I12038012ff5a60512408b114db22f2638fd135b1
    Closes-Bug: #1289496