cinderclient.exceptions.ClientException fails on py34 if message is not provided
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-cinderclient |
Fix Released
|
Medium
|
Matt Riedemann |
Bug Description
This fails on python 3.4 if the message kwarg evaluates to False:
because self.__
You can see the failure here in a unit test that hit this:
2015-08-04 19:38:16.567 | FAIL: cinderclient.
2015-08-04 19:38:16.567 | tags: worker-3
2015-08-04 19:38:16.567 | -------
2015-08-04 19:38:16.567 | Empty attachments:
2015-08-04 19:38:16.567 | stderr
2015-08-04 19:38:16.567 | stdout
2015-08-04 19:38:16.568 |
2015-08-04 19:38:16.568 | Traceback (most recent call last):
2015-08-04 19:38:16.568 | File "/home/
2015-08-04 19:38:16.568 | ex = exceptions.
2015-08-04 19:38:16.568 | File "/home/
2015-08-04 19:38:16.568 | request_
2015-08-04 19:38:16.568 | File "/home/
2015-08-04 19:38:16.568 | self.message = message or self.__
2015-08-04 19:38:16.568 | AttributeError: type object 'ClientException' has no attribute 'message'
Changed in python-cinderclient: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Matt Riedemann (mriedem) |
Changed in python-cinderclient: | |
milestone: | none → 1.4.0 |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/209258
Review: https:/