-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
celery: UnicodeEncodeError: 'ascii' codec can't encode character u'\u9a6c' in position 0: ordinal not in range(128) #2304
Comments
Hi Yongshengma Converting the image made the volumedriver trigger the create event on which the Framework responds. The Framework enforces ascii encoding when saving objects to the OVSDB Arakoon (through the ujson serialization) The following suggestion will not work if the Framework already stored the key inside Arakoon as decoding it would be impossible with the current implementation. If this is the case, reply back to this ticket and I'll see how I can assist you further.
If the snippet above raises any exception regarding decoding, we will have to resolve it differently. Side note: For future exceptions: it's better to log the stacktrace as seen in the Best regards |
I replicated this issue in a test env, so look at these lines please:
The returned number of Happenly a task
May that failed one be the removed one with special chars? More context:
|
I;m afraid you made a typo mistake on
You can see that heterogeneous vdisk name shows up in the list, but it has actually been removed by me. Continue
|
|
Hi Yongshenga I indeed made some mistakes while writing the small test out.
But it looks like i have the information I need. The VDisk object can be retrieved through a list lookup ( The StorageRouter lookup exception puzzles me. I have no clue on what went wrong during that look up. The only thing coming to mind is that an old entry is still cached for that volume and the cluster shrank, but this is an unlikely scenario. If anything it points to #2289 which is also lacking in context. |
I can still access vdisk list from each router's vdisk tab, so it's not a big deal at this moment. I will keep on following this issue. Thanks for your reference. Best regards |
Hello,
I converted a qcow2 image to a raw image into/under vpool mount point, but the device name contains a few Chinese characters. Then vdisks list page became empty and its api returns 500 error.
I guess the Chinese chars could be the cause to this issue, so I removed that raw file such as
rm /mnt/vpool/xxx.raw
. However, the log above still coming out when vdisks list page is accessed. Of coz the page is still empty.Is that device name saved somewhere?
Best regards
Yongsheng
The text was updated successfully, but these errors were encountered: