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>
Reviewed: https:/ /review. openstack. org/116226 /git.openstack. org/cgit/ openstack/ horizon/ commit/ ?id=a212ef399f7 8633d7627b633f7 33f8c525c30aa3
Committed: https:/
Submitter: Jenkins
Branch: master
commit a212ef399f78633 d7627b633f733f8 c525c30aa3
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 3f35c0c172e39fd f237fa42278
Change-Id: Id6c620ca51f770
Co-Authored-By: Timur Sufiev <email address hidden>