Comment 5 for bug 1301374

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

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

commit a212ef399f78633d7627b633f733f8c525c30aa3
Author: Vlad Okhrimenko <email address hidden>
Date: Fri Aug 22 14:04:16 2014 +0300

    Uniquify horizon messages returned in a single response

    A network operation can fail because of different
    reasons - yet in many places just one error message
    is provided. Combined with too broad exception clause,
    and incorrect assumptions on the reasons of failure
    (e.g. Neutron service being unavailable causes all
    other sorts of errors like inability to Allocate IP
    or Associate it) this leads to multiple errors when just one
    would suffice. The fix aims to provide sensible error
    messages in case the network service is down. This includes
    returning only unique messages in a single response.

    Partial-Bug: #1301374
    Change-Id: Id6c620ca51f7703f35c0c172e39fdf237fa42278
    Co-Authored-By: Timur Sufiev <email address hidden>