Heat now consistently formats error messages in returned HTTP json
and heatclient HTTPException makes every attempt to capture these
messages.
This means that the safest way to display an error or validation
message from Heat is to rely on the existing behaviour of
Horizon's exceptions.handle.
Change-Id: I80cdb67df87cb5192f220bc78a156d6e4113112f
Closes-Bug: #1241395
(cherry picked from commit 2c7db077b265c25573bfef73586a539fa639f65f)
Reviewed: https:/ /review. openstack. org/100416 /git.openstack. org/cgit/ openstack/ horizon/ commit/ ?id=a29cdbc48f6 5f8e9b648b8ab03 a8a3bdd60663b9
Committed: https:/
Submitter: Jenkins
Branch: stable/icehouse
commit a29cdbc48f65f8e 9b648b8ab03a8a3 bdd60663b9
Author: Steve Baker <email address hidden>
Date: Mon Apr 14 09:15:37 2014 +1200
Fix formatting of heat exceptions
Heat now consistently formats error messages in returned HTTP json
and heatclient HTTPException makes every attempt to capture these
messages.
This means that the safest way to display an error or validation
message from Heat is to rely on the existing behaviour of
Horizon's exceptions.handle.
Change-Id: I80cdb67df87cb5 192f220bc78a156 d6e4113112f 573bfef73586a53 9fa639f65f)
Closes-Bug: #1241395
(cherry picked from commit 2c7db077b265c25