[Openstack-operators] deleted image still showing up

Fischer, Matt matthew.fischer at twcable.com
Thu Jul 31 14:21:46 UTC 2014


Thanks,

I made the changes this morning, the image is gone, and nothing blew up. I'm always a bit nervous live editing a production DB…

From: Jesse Pretorius <jesse.pretorius at gmail.com<mailto:jesse.pretorius at gmail.com>>
Date: Wednesday, July 30, 2014 11:25 PM
To: Abel Lopez <alopgeek at gmail.com<mailto:alopgeek at gmail.com>>
Cc: Matt Fischer <matthew.fischer at twcable.com<mailto:matthew.fischer at twcable.com>>, "openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>" <openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>>
Subject: Re: [Openstack-operators] deleted image still showing up

Agreed. You may also wish to update deleted_at=now() to keep a record of when you did it.

Sent from my iPhone

On 30 Jul 2014, at 10:28 PM, Abel Lopez <alopgeek at gmail.com<mailto:alopgeek at gmail.com>> wrote:

If your UUID is correct, I’d just update the DB to say deleted=1.
It’s possible that you’re looking at images that have the same “display name” but different UUID’s.
If you confirm the UUID is the same, just do
update images set deleted=1 where id=“${UUID}”;

On Jul 30, 2014, at 12:54 PM, Fischer, Matt <matthew.fischer at twcable.com<mailto:matthew.fischer at twcable.com>> wrote:

environment: Icehouse release on Ubuntu

We have a glance image that is in a "deleted" state but still shows up in Horizon. The image is in a state where I cannot move it one way or the other and I'd like it gone.  The state in the database is "deleted", the image itself is gone from disk (ceph backing), but still shows up in image lists and in Horizon. The only differences I see in the database when I compare this deleted image to others is that the "deleted_at" field is NULL and "deleted" is 0, not 1. I assume that the deletion returned a failure status and the database was not updated. Before I go and mess with a production database, I'd like to get an opinion on a fix. My current best guess is to enter a date for 'deleted_at' and set 'deleted' to 1 in the DB. Alternatively I can set the status back to active and make an empty file with the id in ceph and use the CLI/API to fulfill the delete.

Opinions?


Anything below here is not from me-----

________________________________
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org<mailto: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/20140731/b6326c89/attachment.html>


More information about the OpenStack-operators mailing list