I ran into a very similar issue when debug was enabled. Tempest testing was running using unicode tests resulted in the following stacktrace - http://paste.openstack.org/show/726897
These were the tests executed:
* cinder_tempest_plugin.api.volume.test_volume_unicode.CinderUnicodeTest.test_snapshot_create_volume_description_non_ascii_code
* cinder_tempest_plugin.api.volume.test_volume_unicode.CinderUnicodeTest.test_create_delete_unicode_volume_name
The python version running the cinder-volume service and the tempest tests is Python 2.7.12
To resolve the issue I simply enabled "use_json" in the cinder.conf when debug is enabled. This converts all log output to json which resolved the issue. A fix without needing to convert the logs to JSON would be fantastic however using the json option when debug is enabled seems to be a suitable workaround for now.
I ran into a very similar issue when debug was enabled. Tempest testing was running using unicode tests resulted in the following stacktrace - http:// paste.openstack .org/show/ 726897
These were the tests executed: tempest_ plugin. api.volume. test_volume_ unicode. CinderUnicodeTe st.test_ snapshot_ create_ volume_ description_ non_ascii_ code tempest_ plugin. api.volume. test_volume_ unicode. CinderUnicodeTe st.test_ create_ delete_ unicode_ volume_ name
* cinder_
* cinder_
The python version running the cinder-volume service and the tempest tests is Python 2.7.12
To resolve the issue I simply enabled "use_json" in the cinder.conf when debug is enabled. This converts all log output to json which resolved the issue. A fix without needing to convert the logs to JSON would be fantastic however using the json option when debug is enabled seems to be a suitable workaround for now.