[openstack-dev] Fw: [Glance] Is the 'killed' state ever set in v2?
mark.washenberger at markwash.net
Sun Jan 26 14:36:36 UTC 2014
It does not seem very ReSTful--or very usable, for that matter--for a
resource to be permanently modified when you a PUT fails. So I don't think
we need the 'killed' status. It was purposefully left out of v2 images,
which is not just a reskin of v1.
Perhaps there is still a bug where an image is getting stuck in 'saving' or
some other state when a PUT fails?
On Sun, Jan 26, 2014 at 5:10 AM, David Koo <kpublicmail at gmail.com> wrote:
> Hi Fei,
> Thanks for the confirmation.
> > I think you're right. The 'killed' status should be set in method
> > if there is an upload failure, see
> I think you meant:
> (the safe_kill() call) right?
> > ------------------ Original ------------------
> > From: "David Koo"<kpublicmail at gmail.com>;
> > Date: Jan 26, 2014
> > To: "OpenStack Development Mailing
> > List"<openstack-dev at lists.openstack.org>;
> > Subject: [openstack-dev] [Glance] Is the 'killed' state ever set in v2?
> > Hi All,
> > While trying to work on a bug I was trying to simulate some image
> > download failures and found that apparently the 'killed' state is never
> > set using v2 APIs.
> > If I understand correctly, a file upload goes to
> > api.v2.image_data.ImageDataController.upload and goes all the way to
> > store.ImageProxy.set_data which proceeds to write to the backend store.
> > If the backend store raises an exception it is simply propagated all the
> > way up. The notifier re-encodes the exceptions (which is the bug I was
> > looking at) but doesn't do anything about the image status.
> > Nowhere does the image status seem to get set to 'killed'.
> > Before I log a bug I just wanted to confirm with everybody whether or
> > not I've missed out on something.
> > Thanks.
> > --
> > Koo
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev