fail to decode unicode error message from hypervisor

Bug #1419595 reported by Hiroki Aramaki
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Low
Hiroki Aramaki
oslo.vmware
Confirmed
Low
Unassigned

Bug Description

summary :
If VMware vCneter return unicode error message
openstack can handle this error message but not human readable message.
nova should decode that message and write to log .

Version : 2014.2.2 and 2015.1

nova-compute write following error message when Japanese vCenter return Japanese error message.

FileNotFoundException: \u30d5\u30a1\u30a4\u30eb [NFSDS] 192.168.1.1_base/cf9ef4db-2e30-4471-b603-c8dedcd88f65 \u304c\u898b\u3064\u304b\u308a\u307e\u305b\u3093\u3067\u3057\u305f

Tags: i18n vmware
Changed in nova:
assignee: nobody → Hiroki Aramaki (h-aramaki)
Changed in nova:
status: New → Confirmed
importance: Undecided → Low
Changed in oslo.vmware:
status: New → Confirmed
importance: Undecided → Low
Changed in nova:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.