Bug 970053 - Bad error on running glance commands with malformed image ID
Summary: Bad error on running glance commands with malformed image ID
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-glanceclient
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 4.0
Assignee: Flavio Percoco
QA Contact: Tzach Shefi
URL:
Whiteboard: storage
Keywords: Triaged
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-03 11:52 UTC by Daniel Paikov
Modified: 2016-04-27 03:06 UTC (History)
6 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2013-12-20 00:04:22 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1859 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2013-12-21 00:01:48 UTC
OpenStack gerrit 37825 None None None Never
Launchpad 1178233 None None None Never
Launchpad 1190606 None None None Never

Description Daniel Paikov 2013-06-03 11:52:42 UTC
glance commands with a malformed image ID produce the following error:


[root@orange-vdsf ~(keystone_admin)]# glance image-delete 1
argument 2 to map() must support iteration

[root@orange-vdsf ~(keystone_admin)]# glance image-update 1 
argument 2 to map() must support iteration

[root@orange-vdsf ~(keystone_admin)]# glance image-download 1
argument 2 to map() must support iteration

Comment 6 Jakub Ruzicka 2013-11-20 12:17:53 UTC
I've built python-glanceclient-0.12.0-1.el6ost which includes the upstream fix.

Comment 9 Dafna Ron 2013-12-11 17:34:11 UTC
root@cougar06 ~(keystone_admin)]# glance image-delete 1234567890
Request returned failure status.
No image with a name or ID of '1234567890' exists.
[root@cougar06 ~(keystone_admin)]# 

moving to verified on 
openstack-glance-2013.2-4.el6ost.noarch

Comment 11 errata-xmlrpc 2013-12-20 00:04:22 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/RHEA-2013-1859.html


Note You need to log in before you can comment on or make changes to this bug.