'counter_name' is not defined in cloudkittyclient and the wrong exceptions are caught

Bug #1645380 reported by Luka Peschke
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cloudkitty
Fix Committed
Undecided
Luka Peschke

Bug Description

In the different shell.py files of the cloudkittyclient, HTTP exceptions are caught. These exceptions are defined in cloudkittyclient/exc.py. But the exceptions that could possibly be raised are defined in cloudkittyclient/apiclient/exceptions.py. Thus, the except block which should raise the Exception with a specific error message is never executed, and the HTTP exception is risen as is.

If the 'except' block were to be executed, 'args.counter_name' would be used to create the specific error message. But this attribute is never defined:

AttributeError: 'Namespace' object has no attribute 'counter_name'

Changed in cloudkitty:
assignee: nobody → Luka Peschke (luka-peschke)
Changed in cloudkitty:
status: New → In Progress
Changed in cloudkitty:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-cloudkittyclient 1.0.0

This issue was fixed in the openstack/python-cloudkittyclient 1.0.0 release.

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.