returning the wrong error types for CFN API exceptions

[Liang Chen]

Please see comment from Zane on https://review.openstack.org/#/c/31756/3

[Steven Hardy (shardy)]

I'm confused, why have we got a bug report about a bug which hasn't been merged yet?

Seems like you just need to fix up the patch in the review above to align with one of the existing CFN exception/error types?

[Zane Bitter (zaneb)]

The bug is that existing ones are wrong too. e.g. StackExists should return AlreadyExists, not InvalidParameterValue.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/32723
Committed: http://github.com/openstack/heat/commit/7b9c2312cd323c0cfc80f86c0385ff2c9f8e5daf
Submitter: Jenkins
Branch: master

commit 7b9c2312cd323c0cfc80f86c0385ff2c9f8e5daf
Author: Liang Chen <email address hidden>
Date: Wed Jun 12 21:47:05 2013 +0800

    fix an CFN API and AWS error mapping

    StackExists should return AlreadyExists, not InvalidParameterValue

    Fixes bug #1188473

    Change-Id: Ia969cddc1b61caa13f4f70bcc29f3160595a779b