AgentException errors incorrect logging output

[Steve McLellan]

If an error occurs running agent scripts, the message is received by the engine, the AgentException constructed sets the message information to self.message_info, which means that it gets hidden when it's logged.

For instance:

try:
  raise AgentException({"message": "Errors happened", "errorCode": 100})
except Exception:
  logging.exception("An error happened")
ERROR:root:An error happened
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
AgentException

I think removing the message_info state would be enough to allow the error to be logged properly.

This can be part of https://blueprints.launchpad.net/murano/+spec/improve-engine-logging

[Openstack Gerrit (openstack-gerrit)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/92392
Committed: https://git.openstack.org/cgit/stackforge/murano-api/commit/?id=289a1f886d9faa0fbebc296e949ae119bb8c6506
Submitter: Jenkins
Branch: master

commit 289a1f886d9faa0fbebc296e949ae119bb8c6506
Author: Steve McLellan <email address hidden>
Date: Tue May 6 10:26:10 2014 -0500

    Allow AgentExceptions to be logged properly

    Remove the special handling in AgentException so that
    the default Exception behavior is used when logging, and
    details are shown.

    Partially implements blueprint improve-engine-logging
    Closes-Bug: #1316360
    Change-Id: I9730c3e0733f1d6e7d1e40a03aea8499c9605093