I ran into a similar issue in Havana, but that was because we were doing some 'behind-the-scenes' modification of the image (format conversion) Once we stopped that, the issue went away. What is your glance store configured as? > On Feb 2, 2016, at 3:05 PM, Liam Haworth <liam.haworth at bluereef.com.au> wrote: > > Hey All, > > This sounds like an old bug after trying to google it but everything I found doesn't really seem to help. I'm trying to upload a 2.5GB QCOW2 image to glance to be used by users, the upload goes fine and in the glance registry logs I can see that it has successfully saved the image but then it does this > > 2016-02-03 09:51:49.607 2826 DEBUG glance.registry.api.v1.images [req-5ba18ea3-5777-4023-9f85-040aca48dfa7 --trunced-- - - -] Updating image 03a920ce-7979-4439-ab71-bc3dd34df3d3 with metadata: {u'status': u'killed'} update /usr/lib/python2.7/dist-packages/glance/registry/api/v1/images.py:470 > > What reasons are their for it to do this to an image that just successfully uploaded? > > Thanks, > > Liam Haworth. > -- > Liam Haworth | Junior Software Engineer | www.bluereef.com.au <http://www.bluereef.com.au/> > _________________________________________________________________ > T: +61 3 9898 8000 <> | F: +61 3 9898 8055 <> > > <> > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160202/f4842c62/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: Message signed with OpenPGP using GPGMail URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160202/f4842c62/attachment.pgp>