Deployment history should contain message of a failed task

[Julia Aranovich]

Deployment history data (GET /api/transactions/<transaction_id>/deployment_history response) should contain 'message' attribute at least for a failed deployment task (task status is 'error').

A possible solution is to keep this error message into existing task's.
At the same time, 'custom' attribute.
But this 'custom' attribute should be merged into root task attributes and doesn't exist in the API response.

[Julia Aranovich (jkirnosova)]

Raised to high as far as 'message' is critical information for a failed task (deployment).

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/375513
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=8ee56f4dccb313574deb8017fb6f2b1280187c28
Submitter: Jenkins
Branch: master

commit 8ee56f4dccb313574deb8017fb6f2b1280187c28
Author: Bulat Gaifullin <email address hidden>
Date: Fri Sep 23 17:12:13 2016 +0300

    Merge property 'custom' of deployment_history with root

    The custom property was designed to store all attributes
    witch does not define in model. And durring serialization
    this properties should be added to root like other properties.

    Partial-Bug: 1597470
    Change-Id: I42c6a9ad1d8f7f62a5ab542a4877d69cae7a3cd5

[Georgy Kibardin (gkibardin)]

The information you need is already in place, you just need to:
/api/transactions/<id>/deployment_history?include_summary=1
and the message is 'error_msg' inside of 'summary'.