WSME 0.5b5 returns correct response status codes -- breaking unit tests
Bug #1227264 reported by
gordon chung
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Critical
|
Julien Danjou |
Bug Description
WSME 0.5b5 was updated to return more accurate response status codes. we need to fix our unit tests to accept them.
should be related to these patches:
https:/
https:/
Changed in ceilometer: | |
assignee: | nobody → gordon chung (chungg) |
summary: |
- WSME 0.5b5 returns correct response status codes + WSME 0.5b5 returns correct response status codes -- breaking unit tests |
description: | updated |
Changed in ceilometer: | |
assignee: | gordon chung (chungg) → Julien Danjou (jdanjou) |
Changed in ceilometer: | |
importance: | Undecided → Critical |
milestone: | none → havana-rc1 |
Changed in ceilometer: | |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | havana-rc1 → 2013.2 |
To post a comment you must log in.
secondary issue is that when we pass in translatable text to wsme.exc. ClientSideError (), it implodes.
in wsme, https:/ /github. com/stackforge/ wsme/blob/ master/ wsme/exc. py#L15
it checks for type which appears to be unicode but is really <class 'ceilometer. openstack. common. gettextutils. Message' >. when it tries to convert gettexutils.Message to unicode six.u(), it breaks.