Bug 1041806 - [RFE][glance]: Error status for images and image state management
Summary: [RFE][glance]: Error status for images and image state management
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/glan...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 19:24 UTC by RHOS Integration
Modified: 2015-03-19 17:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:20:54 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 19:24:49 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/glance/+spec/image-error-state-management.

Description:

Instead of "killing" an image when something goes wrong during data upload, we need a good way to make it obvious the image failed to upload and notify the user. I propose we add an image error state and take a deeper look at image states in general.

There are a couple of use cases where this is important.

- Snapshots through nova
 When a snapshot fails the image could be set to ERROR instead of being deleted/killed. This way users can see that a snapshot failed.

- Copy-from images
 If a copy from image fails during the data copying by the async worker then there is no way for a user to know it failed and it would be unintuitive for the image resource to disappear.

- Failed uploads
 In addition to error responses from Glance when an upload fails, it would be nice for that image resource to not be deleted automatically and have a way for the user to know it had errored. This way uploads could be retried without having to create a whole new image entity.

Specification URL (additional information):

None


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