yahoo-eng-team team mailing list archive

[Augustina Ragwitz <1545729@xxxxxxxxxxxxxxxxxx>]

This is a feature request. If you'd like to move forward with using
4-byte unicode characters on the backend, please submit a spec for doing
so. If the issue is that the returned error is confusing and you'd like
that improved, that is a valid bug and this issue can be reopened with
that as the bug description.

** Tags added: compute

** Summary changed:

- 4 byte unicode handling for entity names
+ Nova should use 4 byte unicode for entity names

** Summary changed:

- Nova should use 4 byte unicode for entity names
+ Use 4 byte unicode for entity names in mysql

** Changed in: nova
       Status: New => Invalid

-- 
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):
  Invalid

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