yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #32225
[Bug 1447322] [NEW] Attempting to reactivate a queued image returns a 403
Public bug reported:
Overview:
When attempting to reactivate a queued image (one without an image file) returns a "'403 Forbidden - Not allowed to reactivate image in status 'queued'".
Steps to reproduce:
1) Register a new image as user
2) Without uploading an image file, reactivate the image as admin via:
POST /images/<image_id>/actions/reactivate
3) Notice that a "'403 Forbidden - Not allowed to reactivate image in status 'queued'" is returned
Expected:
Currently a 400 response should be returned with the same message per spec, but this is expected to be changed to a 409
Actual:
A 403 response is returned
** Affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1447322
Title:
Attempting to reactivate a queued image returns a 403
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
Overview:
When attempting to reactivate a queued image (one without an image file) returns a "'403 Forbidden - Not allowed to reactivate image in status 'queued'".
Steps to reproduce:
1) Register a new image as user
2) Without uploading an image file, reactivate the image as admin via:
POST /images/<image_id>/actions/reactivate
3) Notice that a "'403 Forbidden - Not allowed to reactivate image in status 'queued'" is returned
Expected:
Currently a 400 response should be returned with the same message per spec, but this is expected to be changed to a 409
Actual:
A 403 response is returned
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1447322/+subscriptions
Follow ups
References