Handing required for 4 byte unicode characters in Nova
If any operation is executed with 4byte unicode name, Nova 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://
<class 'oslo_db.
This happens becuase Nova uses mysql database for storing different entity details and
MySql does not support 4 byte unicode due to its utf8 character set.
To handle 4 byte unicode character set, we need to update mysql characterset from utf8 to utf8mb4.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Sheel Rana
- Direction:
- Needs approval
- Assignee:
- Sheel Rana
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
| Bug #1545729: Proper error message to user in case 4 byte unicode characters are used for entity names. | In Progress |
Sprints
Whiteboard
We are going to discuss this issue in cross project meeting.
Till then we can keep this BP as it is.
Once fix strategy is fixed, I will go ahead and add supprot for 4 byte unicode characters.
In case utf8 to utf8mb4 update is not suggested, we will use oslo-db exception handling for fixing this issue through Bug#1545729
cross project spec: https:/
