ecf2241668
For many releases we have seen overall deployment and workflow exections that timeout throw a json decode error. This is usually because either the mistral execution completely failed (unhandled exception), something during the deployment hangs (bad network config), or the --timeout was less than the time it takes to run an action. If we get an exception waiting for timeouts that isn't already a websocket timeout or something to that effect, we should catch it and print some useful messaging that the user can use to begin their troubleshooting. Change-Id: Ie239f3fc11bbf95dc9af9786b288f6e8aef1193a Closes-Bug: #1882134 |
||
---|---|---|
config-generator | ||
doc | ||
releasenotes | ||
tripleoclient | ||
zuul.d | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
CONTRIBUTING.rst | ||
LICENSE | ||
README.rst | ||
babel.cfg | ||
bindep.txt | ||
lower-constraints.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
About tripleoclient
General information
tripleoclient is an OpenStackClient (OSC) plugin implementation that implements commands useful for TripleO and the install and management of both an undercloud and an overcloud.
See the TripleO Documentation for details on using tripleoclient.
See the Release Notes