This bug was fixed in the package python-oslo.context - 2.2.0-2ubuntu1~cloud0

 python-oslo.context (2.2.0-2ubuntu1~cloud0) trusty-mitaka; urgency=medium
   * New update for the Ubuntu Cloud Archive.
 python-oslo.context (2.2.0-2ubuntu1) xenial; urgency=medium
   * Adding support unicode for older type of user id (LP: #1507937)
     - d/p/0001-Ensure-to_dict-supports-unicode.patch

** Changed in: cloud-archive/mitaka
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs

  Tenant does not support non-ascii characters

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in oslo.context:
  Fix Released
Status in python-oslo.context package in Ubuntu:
Status in python-oslo.context source package in Xenial:
  Fix Released

Bug description:

  Affected to trusty-mitaka, only has older form of user id

  Assume that there is unicode user id (like John Gāo) from ldap on trusty-kilo 
  and Upgraded to trusty-mitaka.

  I can't command nova list with 500 error and nova-api log show us
  unicode error like below

  UnicodeEncodeError: 'ascii' codec can't encode character u'\xe1' in
  position 1: ordinal not in range(128)

  [Test Case]

  TBD for detail script or info

  0. proper ldap setting(accounts etc..) with user id has unicode character as 
  1. deploy trusty-kilo env
  - without ldap config,
  - if i set ldap config at the beginning, there is error because by default 
config blocks CRUD user on ldap)
  2. setting ldap configuration
  3. remove CRUD block on keystone.conf temporarily
  4. need to set up password for nova, cinder, etc service accounts
  - openstack user set --password-prompt nova ( for all services )
  - you can check password in each services configuration file
  5. upgrade to trusty-mitaka
  6. source novarc
  7. nova list

  you can get 500 error


  This patch is simple, but need to restart every api service e.g nova-
  api, glance-api, cinder-api etc because they are handling user id for
  getting information respectively. This causes temporarily service


  If I deployed trusty-mitaka in the beginning, keystone user id is form
  of uuid, so no need to patch this basically.

  [Original description]
  When Tenant name contains any non-acsii characters (such as Chinese), calling 
oslo_context/ method will cause a unicodeEncodeError: 'ascii' 
codec can't encode characters in position 0-3: ordinal not in range(128).

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to