Bug 888961

Summary: Can't create glance image with non-ASCII name
Product: Red Hat OpenStack Reporter: Russell Bryant <rbryant>
Component: python-glanceclientAssignee: Jakub Ruzicka <jruzicka>
Status: CLOSED ERRATA QA Contact: Attila Fazekas <afazekas>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: apevec, dallan, fpercoco
Target Milestone: snapshot5Keywords: i18n, Triaged
Target Release: 2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 0.8.0-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-04 17:58:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Russell Bryant 2012-12-19 22:07:56 UTC 
Description of problem:

Attempting to create an image in glance with a non-ASCII name fails.


Version-Release number of selected component (if applicable):

openstack-glance-2012.2.1-1.el6ost.noarch
python-glance-2012.2.1-1.el6ost.noarch
python-glanceclient-0.5.1-1.el6.noarch


Steps to Reproduce:

[root@rhel ~(keystone_username)]# glance image-create      --container-format  bare --disk-format qcow2      --name "El Niño" --copy-from http://berrange.fedorapeople.org/images/2012-11-15/f17-x86_64-openstack-sda.qcow2
'ascii' codec can't decode byte 0xc3 in position 28: ordinal not in range(128)
Comment 1 Russell Bryant 2012-12-19 22:12:01 UTC 
and probably the same bug exposed here ...

# glance image-update --name "El Niño" 5701fd2f-d1cb-4bcb-bb5d-fa9e9a4bbd51
'ascii' codec can't decode byte 0xc3 in position 28: ordinal not in range(128)
Comment 3 Alan Pevec 2012-12-21 17:44:45 UTC 
Looks like there's upstream work required to cleanup i18n issues across all openstack clients (see also novaclient bug 888483)
Comment 6 Yaniv Kaul 2013-02-20 08:20:21 UTC 
QE: worth adding a test case for Tempest for this.
Comment 8 Attila Fazekas 2013-03-17 18:12:26 UTC 
ykaul: OK

Working.
Comment 10 errata-xmlrpc 2013-04-04 17:58:46 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0706.html