Back to bug 1033190

Who When What Removed Added
RHEL Program Management 2013-11-21 16:48:58 UTC Target Release --- 4.0
Jamie Lennox 2013-11-22 06:57:37 UTC Status NEW ASSIGNED
CC jlennox
Assignee rhos-maint jlennox
Link ID Launchpad 1253905
Alan Pevec 2013-12-05 13:33:19 UTC Priority unspecified medium
Target Milestone --- rc
Link ID OpenStack gerrit 60106
RHEL Program Management 2013-12-05 18:19:47 UTC Target Release 4.0 5.0
Jamie Lennox 2014-01-07 21:41:36 UTC Status ASSIGNED ON_DEV
John Skeoch 2014-01-13 01:07:44 UTC CC hateya
Jamie Lennox 2014-02-04 21:42:28 UTC Keywords Triaged
Nathan Kinder 2014-03-13 15:46:04 UTC Status ON_DEV POST
CC nkinder
Target Milestone rc Upstream M2
Nathan Kinder 2014-06-13 15:18:18 UTC Status POST MODIFIED
Fixed In Version openstack-keystone-2014.1-4.el7ost
Link ID OpenStack gerrit 60106 OpenStack gerrit 57851
Nathan Kinder 2014-06-13 15:18:51 UTC Link ID OpenStack gerrit 57850
errata-xmlrpc 2014-06-16 15:49:06 UTC Status MODIFIED ON_QA
Bruce Reeler 2014-06-25 02:23:00 UTC CC breeler
Flags needinfo?(jlennox)
Lon Hohberger 2014-06-25 16:22:00 UTC Status ON_QA MODIFIED
errata-xmlrpc 2014-06-26 12:50:35 UTC Status MODIFIED ON_QA
Jamie Lennox 2014-06-30 05:28:02 UTC Doc Text Cause: Some errors including those thrown from the database are reported in an ASCII byte string format. This error message is included in some failures and so the error message would display the byte escaped output and UTF-8 values would be lost.

Consequence: UTF-8 characters would appear escaped eg \\u2013 in messages instead of the correct UTF-8 character.

Fix: Whenever an error message is produced attempt to UTF-8 decode it. This will have no effect when there is no UTF-8 characters, but will ensure any that are present will be correctly rendered.

Result: Output displays full UTF-8 characters in error messages.
Flags needinfo?(jlennox)
Bruce Reeler 2014-06-30 07:15:02 UTC Doc Text Cause: Some errors including those thrown from the database are reported in an ASCII byte string format. This error message is included in some failures and so the error message would display the byte escaped output and UTF-8 values would be lost.

Consequence: UTF-8 characters would appear escaped eg \\u2013 in messages instead of the correct UTF-8 character.

Fix: Whenever an error message is produced attempt to UTF-8 decode it. This will have no effect when there is no UTF-8 characters, but will ensure any that are present will be correctly rendered.

Result: Output displays full UTF-8 characters in error messages.
Some errors, including those thrown from the database, are reported in an ASCII byte string format. This error message is included in some failures and so the error message would display the byte escaped output and UTF-8 values would be lost. As a consequence, UTF-8 characters would appear escaped, for example \\u2013 in messages instead of the correct UTF-8 character.

This has been fixed to ensure that UTF-8 characters that are present will be correctly rendered. Now the output displays full UTF-8 characters in error messages.
Udi Kalifon 2014-07-03 14:23:16 UTC CC dyocum, ukalifon
QA Contact ajeain ukalifon
Flags needinfo?(dyocum)
Dan Yocum 2014-07-03 15:05:41 UTC Flags needinfo?(dyocum)
Udi Kalifon 2014-07-06 08:41:53 UTC Status ON_QA VERIFIED
errata-xmlrpc 2014-07-07 15:00:37 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2014-07-08 15:23:46 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2014-07-08 11:23:46 UTC
Perry Myers 2016-04-27 04:23:26 UTC CC pmyers

Back to bug 1033190