BP implementation will require much time because of migration related changes. Spec for same is already in discussion. Please refer below:
https://review.openstack.org/#/c/280371/ So, I created this bug for better message to user in case 4 byte unicode is used in entity names as short term fix. I will update the issue details and reopen it for short time fix. Thanks!! ** Changed in: nova Status: Invalid => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1545729 Title: Use 4 byte unicode for entity names in mysql Status in OpenStack Compute (nova): In Progress Bug description: mysql database does not support 4 byte unicode due to its utf8 character set. If any operation is executed with 4byte unicode name, it reports 500 error without any proper error message to user. This will be confusing for user as no information is present about why this issue occurred. Please refer below for details: nova secgroup-create sheel 🌋 ERROR (ClientException): Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. <class 'oslo_db.exception.DBError'> (HTTP 500) (Request-ID: req-a4eef1d6-11fa-4188-b116-ffdf728e04f4) Bug can be reproduced by simply using 4byte unicode characters in name of security group. This is 100% reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1545729/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
