Ask Your Question

Glance unable to download images, cannot create instances.

asked 2013-06-05 05:19:26 -0600

fweeky gravatar image

updated 2013-06-05 05:30:32 -0600

I'm using: Grizzly Keystone+Nova+Quantum+Cinder+Glance version 2013.1 on a single node, though might expand to multiple nodes later (if I get this working).

I add a CirrOS or Ubuntu QCOW2 image using the Horizon dashboard. Glance logs look fine. The glance image IDs appear in the glance directory, and 'glance image-list' shows expected output:

| ID                                   | Name     | Disk Format | Container Format | Size    | Status |
| 960aa9a4-78cf-417b-8171-3a2bdab103f3 | CirrusOS | qcow2       | bare             | 9761280 | active |

I decide to create an instance. This is where things go awry in nova, as per (this verbose trace and log). The instance is now stuck on 'scheduled'. [redacted.hostname] is my FQDN and X.X.X.X is my globally routable IP.

I'm also seeing an issue with Cinder when using the rootwrap configuration, as opposed to pure sudo. Whenever I start Cinder with root_wrap=/etc/cinder/rootwrap.conf or rootwrap.conf, I get (this error) and Cinder refuses to do anything through rootwrap. rootwrap.conf and volume.filters are correct as per their repository equivalents. Running the commands myself produces (this) output. (glance-api.conf), (glance-registry.conf), (glance-api-paste.ini), (glance-registry-paste.ini), (glance-cache.conf), (glance-scrubber.conf), other Glance configuration files match the defaults from the grizzly repo exactly. (nova.conf), (api-paste.ini), other Nova configuration files match the defaults from the grizzly repo exactly. (cinder.conf), (cinder-api-paste.ini), other Cinder configuration files match the defaults from the grizzly repo exactly.

Note that all config files were processed through s/^#/d and s/^\n/d for conciseness.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2013-06-05 12:15:39 -0600

armando-migliaccio gravatar image

As for the Cinder issue, check file:


it should contain something like this:

# cinder-rootwrap command filters for volume nodes
# This file should be owned by (and only-writeable by) the root user

# cinder/volume/ iscsi_helper '--op' ...
ietadm: CommandFilter, ietadm, root
tgtadm: CommandFilter, tgtadm, root
tgt-admin: CommandFilter, tgt-admin, root
rtstool: CommandFilter, rtstool, root

# cinder/volume/ 'vgs', '--noheadings', '-o', 'name'
vgs: CommandFilter, vgs, root

# cinder/volume/ 'lvcreate', '-L', sizestr, '-n', volume_name,..
# cinder/volume/ 'lvcreate', '-L', ...
lvcreate: CommandFilter, lvcreate, root

# cinder/volume/ 'dd', 'if=%s' % srcstr, 'of=%s' % deststr,...
dd: CommandFilter, dd, root

# cinder/volume/ 'lvremove', '-f', %s/%s % ...
lvremove: CommandFilter, lvremove, root

# cinder/volume/ 'lvdisplay', '--noheading', '-C', '-o', 'Attr',..
lvdisplay: CommandFilter, lvdisplay, root

# cinder/volume/ 'iscsiadm', '-m', 'discovery', '-t',...
# cinder/volume/ 'iscsiadm', '-m', 'node', '-T', ...
iscsiadm: CommandFilter, iscsiadm, root


The error complaint is about a missing 'Filters' section; that makes me think there is something wrong with this file.

As for the Nova issue, it looks like the image location is None. Try:

glance show 960aa9a4-78cf-417b-8171-3a2bdab103f3

That should tell you the URI for the image, and troubleshoot this further.

edit flag offensive delete link more


Thanks for your contribution. Here's my rootwrap.d/volume.filters: - It exactly matches the one in the grizzly repository. And the output of glance show is: - I'm not sure how to troubleshoot from that?

fweeky gravatar imagefweeky ( 2013-06-05 19:20:09 -0600 )edit

Also, note that I have the same problem with every image I add - I just tried downloading the 'raring' image and running glance image-create --name Raring --disk-format=qcow2 --container-format=bare < ./raring-server-cloudimg-amd64-disk1.img. Same problem.

fweeky gravatar imagefweeky ( 2013-06-05 19:32:41 -0600 )edit

Typically Glance endpoints use port 9292. Why are you using port 80? As for the cinder rootwrapper, check also permissions to the file

armando-migliaccio gravatar imagearmando-migliaccio ( 2013-06-06 12:33:51 -0600 )edit

I was using port 9292 - sorry, I cut it off accidentally when removing my IP. The permissions on rootwrap were fine - I was running it as root anyway. I've upgraded to track the SCM builds and cleared my configuration and databases. Hopefully everything will work out when I set it up again tomorrow.

fweeky gravatar imagefweeky ( 2013-06-06 18:57:22 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2013-06-05 05:19:26 -0600

Seen: 1,606 times

Last updated: Jun 05 '13