Tripleoclient failures don't produce enough information

[Jiří Stránský]

E.g. with bug 1734703 we probably had a KeyError issue raised on `openstack overcloud deploy`, but there was no mention of that in the tripleoclient output. All that was printed was that stack was CREATE_COMPLETE, and this:

'ctlplane'
END return value: 1

It took me a while to realize what was going on there :)

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Dougal Matthews (<email address hidden>) on branch: master
Review: https://review.openstack.org/523151
Reason: I have no current plans to come back to this.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit a022a339bea74dc26aebbdceafad46e4f2a2722e
Author: Alex Schultz <email address hidden>
Date: Tue Oct 9 09:51:41 2018 -0600

    Log exceptions that are uncaught

    Since openstackclient usually eats the exceptions, we should at least
    print any that manage to not be caught. We've seen this in the past
    where a deploy is run and the last output is 'password'.

    Change-Id: I3b298ebe60a278c68fa582c47f36f87a94f9f2f8
    Closes-Bug: #1734704

[OpenStack Infra (hudson-openstack)]

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