yahoo-eng-team team mailing list archive

[Kamil Rykowski <kamil.rykowski@xxxxxxxxx>]

Ankit is totally right that 403 is a valid response here. The rfc2616
defines 403 as "The server understood the request, but is refusing to
fulfill it" which is exactly what is happening in this scenario.

The API docs haven't been updated yet [1], as image deactivation is
fresh feature. There is an bug report for it [2] and when it will be
ready it should be more cleaner what status codes can be returned.

[1] http://developer.openstack.org/api-ref-image-v2.html
[2]  https://bugs.launchpad.net/openstack-api-site/+bug/1432342

** Changed in: glance
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1445487

Title:
  Attempting to deactivate a queued image returns a 403

Status in OpenStack Image Registry and Delivery Service (Glance):
  Invalid

Bug description:
  Overview:
  When attempting to deactivate a queued image (one without an image file) returns a "'403 Forbidden - Not allowed to deactivate image in status 'queued'".

  Steps to reproduce:
  1) Register a new image as user
  2) Without uploading an image file, deactivate the image as admin via:
  POST /images/<image_id>/actions/deactivate
  3) Notice that a "'403 Forbidden - Not allowed to deactivate image in status 'queued'" is returned

  Expected:
  A 400 response should be returned with the same message

  Actual:
  A 403 response is returned

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1445487/+subscriptions