** Description changed: [Impact] + 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 env. + 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 above + 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 + 4. need to set up password for nova, cinder, etc service accounts + 5. upgrade to trusty-mitaka + 6. source novarc + 7. nova list + + you can get 500 error [Regression] - + 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 down. [Others] + + If I deployed trusty-mitaka in the beginning, keystone user id is form + of uuid, so no need to patch this basically.
** Tags added: sts sts-sru-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757378 Title: [SRU] Support unicode character for older(prior to kilo) keystone id To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1757378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs