The error message in api response isn't showed in client side

Bug #1652579 reported by Liusheng
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-moganclient
Fix Released
Undecided
Liusheng

Bug Description

If we use nimble with bad request parameters passed to nimble-api, the api will return a BadRequest, with detailed message, but nimbleclient don't parse the response correctly that the error message isn't showed in CLI, it just show a BadRequest(400).

Liusheng (liusheng)
Changed in python-nimbleclient:
assignee: nobody → Liusheng (liusheng)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-nimbleclient (master)

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

Changed in python-nimbleclient:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-nimbleclient (master)

Reviewed: https://review.openstack.org/414858
Committed: https://git.openstack.org/cgit/openstack/python-nimbleclient/commit/?id=74051ad2e19af3b65374dbec489f94c82f297a35
Submitter: Jenkins
Branch: master

commit 74051ad2e19af3b65374dbec489f94c82f297a35
Author: liusheng <email address hidden>
Date: Mon Dec 26 15:13:45 2016 +0800

    Correctly show the reponse's error message in CLI

    Currently, the error message from nimble-api's response isn't showed in
    CLI because wrong exception parse, this change fix it.

    Change-Id: I60ce76ee01ed4a22fa4cd643504f65d35ed07c43
    Closes-Bug: #1652579

Changed in python-nimbleclient:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.