← Back to team overview

openstack team mailing list archive

Re: Glance problem

 

Thanks for help!
 

I have another question. Is there a tutorial for making ubuntu images  with swap partition? In diablo starter guide it says not to make a swap but i want to make one and i don't know how.

 
Andrei-Cosmin Ion
telefon: 0727 768 281
email: andrei_tall@xxxxxxxxx
Munceste ca si cum n-ai muri niciodata, dar ingrijeste-te de sufletul tau ca si cum ai muri maine!


________________________________
 From: Eoghan Glynn <eglynn@xxxxxxxxxx>
To: andrei cosmin <andrei_tall@xxxxxxxxx> 
Cc: openstack@xxxxxxxxxxxxxxxxxxx 
Sent: Monday, April 30, 2012 1:38 PM
Subject: Re: [Openstack] Glance problem
 

Hi Andrei,

The underlying issue is starvation of the storage space used to store
image content(as opposed to the image metadata, which takes up very
little space).

The reason the killed image isn't showing up in the output of glance index
is that non-viable images are sanitized from the list.

If you want to be rid of this image, you can easily find the offending image
ID from the glance registry log, e.g.:

  $ grep killed /var/log/glance/registry.log
  ...
  012-04-30 11:26:48 9198     INFO [sqlalchemy.engine.base.Engine] ('2012-04-30 10:26:48.806445', u'killed', u'e75a8d52-0cc5-481d-b765-3a056d80ad28')

Then you can just delete the metadata directly from the glance registry DB.

For example if using the default sqlite DB, use:

  $ sudo sqlite3 glance.sqlite "DELETE from images where id = 'e75a8d52-0cc5-481d-b765-3a056d80ad28'"

If on the other hand you're using mysql or postgres, just issue the DELETE query
via the appropriate DB client.

Cheers,
Eoghan


> Hi , please help me with this. I try to add a image to glance and i
> receive the following message:
> 
> 
> 
> glance add -A 651abbc762f84e8e9b25baeec35c54bd name=$name
> is_public=true container_format=bare disk_format=raw <
> $imageUploading image 'server'
> ================================================[ 99%] 19.7M/s, ETA
> 0h 0m 0sFailed to add image. Got error:
> The request returned a 413 Request Entity Too Large. This generally
> means that rate limiting or a quota threshold was breached.
> 
> The response body:
> 413 Request Entity Too Large
> 
> The body of your request was too large for this server.
> 
> Image storage media is full: There is not enough disk space on the
> image storage media.
> Note: Your image metadata may still be in the registry, but the
> image's status will likely be 'killed'.
> =================================================[100%] 19.7M/s, ETA
> 0h 0m 0s
> 
> 
> The problem is that i don't know how to delete this metadata (which i
> believe is ocupying my glance). When i try to see my images i see
> only this ones.
> 
> 
> 
> ctrl@ubuntu:~/devstack$ glance index -A
> 651abbc762f84e8e9b25baeec35c54bd
> ID Name Disk Format Container Format Size
> ------------------------------------ ------------------------------
> -------------------- -------------------- --------------
> ffd57095-0bb5-4678-b6ea-2460140d3084 cirros-0.3.0-x86_64-uec-ramdis
> ari ari 2254249
> 48806fc7-2f95-4c83-b7d6-091d59731187 cirros-0.3.0-x86_64-uec-kernel
> aki aki 4731440
> 465d5101-9cdd-4a2c-b55d-534c33949491 cirros-0.3.0-x86_64-uec ami ami
> 25165824
> ctrl@ubuntu:~/devstack$ glance details -A
> 651abbc762f84e8e9b25baeec35c54bd
> 
> Can anybody help?
> 
> 
> 
> Andrei-Cosmin Ion
> telefon: 0727 768 281
> email: andrei_tall@xxxxxxxxx
> Munceste ca si cum n-ai muri niciodata, dar ingrijeste-te de sufletul
> tau ca si cum ai muri maine!
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 

References