98b2414eec
Exceptions from the API were not properly caught when it uses keystone session client path. As a result, error messages in the response body from blazar REST APIs were not displayed. This patch fixes it creating the new SessionClient class, which is basically the same as its parent class, but it can raise BlazarClientException if requests to the blazar server failed. Change-Id: I98ba3949742f2a987beb7e16400608b8ebb60065 Closes-Bug: #1777548
13 lines
568 B
YAML
13 lines
568 B
YAML
---
|
|
fixes:
|
|
- |
|
|
When the blazar CLI client got an error code from the blazar server,
|
|
it didn't display error messages created in the blazar server.
|
|
Instead, it displayed `messages created in keystoneauth`_ with poor
|
|
information. See the `bug report`_ for example.
|
|
It was fixed to display original error messages which include useful
|
|
information.
|
|
|
|
.. _messages created in keystoneauth: https://github.com/openstack/keystoneauth/blob/master/keystoneauth1/exceptions/http.py
|
|
.. _bug report: https://bugs.launchpad.net/blazar/+bug/1777548
|