API wrappers swallow AttributeError inside @properties

[Radomir Dopieralski]

If an AttributeError gets rised inside a @property on an APIResourceWrapper or APIDictWrapper, we will get its "not found" error, even when the original error was from a completely different object. The reason for that is in how __getattr__ works in Python and how any AttributeError from a property gets interpreted as "no such attribute, call __getattr__" by that mechanism.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit 20b414db2fcb3863ad37e3e3fc88d264acdc9f32
Author: Radomir Dopieralski <email address hidden>
Date: Wed Jan 29 14:06:46 2014 +0100

    Don't lose AttributeError in API Wrappers

    Instead of (implicitly) catching the AttributeError, and later
    creating and raising a new one, we just re-raise the original
    exception. This way all the information from the original is
    retained, including the name of the actual object on which it
    happened.

    Change-Id: Idc0c5a8ed5dfca6a8724e393c220baf9960564ed
    Closes-bug: #1274097