There is no way to see what Zaqar messages tripleoclient receives

[Dougal Matthews]

tripleoclient never outputs or logs the zaqar messages it recieves, even with the very verbose --debug flag. This adds the raw zaqar message to that output.

I noticed that a CLI command is printing out a blank message, but it is hard to determine where it comes from. With this output I am able to track it down much more easily.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/575385
Reason: we have gate problems again, please do not restore or recheck, I'll take care of this one when gate is back stable.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/575385
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=658abc2bb8dd9fe896b6f1145b6a9f669320ce3b
Submitter: Zuul
Branch: master

commit 658abc2bb8dd9fe896b6f1145b6a9f669320ce3b
Author: Dougal Matthews <email address hidden>
Date: Thu Jun 14 10:53:59 2018 +0100

    Debug log the raw Zaqar message

    Currently we have no record of this, it would be useful to include it
    when --debug is used on a CLI command.

    Closes-Bug: #1776874
    Change-Id: Iec3267423594db838a5c8c0624aaae23aab0f488

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-tripleoclient 10.3.0 release.