[Yahoo-eng-team] [Bug 1541594] [NEW] Updating image owner to someone else generates a non-intuitive 404 instead of 403
Public bug reported: When an image owner updates an image's owner to someone else, the update is prevented (which is a good thing), but with a 404 "Not Found" (not so good), instead of the 403 "Forbidden". The reason why Glance returns a 404 "Not Found" is because the image is re-fetched after being updated, but as the owner and user differ, the action is forbidden (which get translated into a "not found" because under normal circumstances a forbidden would tip an attacker off to the existence of an image), and the update is never committed. ** 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/1541594 Title: Updating image owner to someone else generates a non-intuitive 404 instead of 403 Status in Glance: New Bug description: When an image owner updates an image's owner to someone else, the update is prevented (which is a good thing), but with a 404 "Not Found" (not so good), instead of the 403 "Forbidden". The reason why Glance returns a 404 "Not Found" is because the image is re-fetched after being updated, but as the owner and user differ, the action is forbidden (which get translated into a "not found" because under normal circumstances a forbidden would tip an attacker off to the existence of an image), and the update is never committed. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1541594/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1449611] [NEW] Attempting to update an image property or add an image tag with 4 byte unicode returns a 500, not a 400
Public bug reported:
Overview:
When attempting to reproduce an the following Launchpad bug
(https://bugs.launchpad.net/glance/+bug/1370954), 4 byte unicode characters
should no longer be allowed for image properties or image tags. Using the
specific value of 'u'Černý'', a 500 response still appears to be returned
instead of a 400 response as we should. This could be a potential issue that
regex didn't catch.
Steps to reproduce:
1) Import an image
2) Attempt to update the image name, passing in 4 byte unicode via:
curl -i /v2/images/image_id -X PATCH -H Content-Type:
application/openstack-images-v2.1-json-patch -H Accept: application/json -H
X-Auth-Token: token -d '[{path: /name, value: u'Černý', op:
replace}]'
3) Notice that a 500 response is returned
4) Attempt to add an image tag, passing in 4 byte unicode via:
curl -i /v2/images/image_id/tags/u'Černý' -X PUT -H Content-Type:
application/json -H Accept: application/json -H X-Auth-Token: token
5) Notice that a 500 response is returned
Expected:
A 400 response should be returned
Actual:
A 500 response is returned for both of these operations
** 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/1449611
Title:
Attempting to update an image property or add an image tag with 4 byte
unicode returns a 500, not a 400
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
Overview:
When attempting to reproduce an the following Launchpad bug
(https://bugs.launchpad.net/glance/+bug/1370954), 4 byte unicode characters
should no longer be allowed for image properties or image tags. Using the
specific value of 'u'Černý'', a 500 response still appears to be returned
instead of a 400 response as we should. This could be a potential issue that
regex didn't catch.
Steps to reproduce:
1) Import an image
2) Attempt to update the image name, passing in 4 byte unicode via:
curl -i /v2/images/image_id -X PATCH -H Content-Type:
application/openstack-images-v2.1-json-patch -H Accept: application/json -H
X-Auth-Token: token -d '[{path: /name, value: u'Černý', op:
replace}]'
3) Notice that a 500 response is returned
4) Attempt to add an image tag, passing in 4 byte unicode via:
curl -i /v2/images/image_id/tags/u'Černý' -X PUT -H Content-Type:
application/json -H Accept: application/json -H X-Auth-Token: token
5) Notice that a 500 response is returned
Expected:
A 400 response should be returned
Actual:
A 500 response is returned for both of these operations
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1449611/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1445608] Re: Deactivated images are not returned for list image requests
This is no longer an issue and can be closed. ** 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/1445608 Title: Deactivated images are not returned for list image requests Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Overview: After deactivating an image, the image owner can no longer see the image in a list images response. Steps to reproduce: 1) Create an image with user A 2) Deactivate the image with an admin 3) List all images, accounting for pagination as needed, with user A via: GET /images 4) Notice that the created (deactivated) image is not returned Expected: Deactivated images are returned in a list images response Actual: Deactivated images are not returned in a list images response To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1445608/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1445487] Re: Attempting to deactivate a queued image returns a 403
Talking with a couple of developers, it appears the upstream docs will be updated as well as the code, changing this to response code to a 409 ** Changed in: glance Status: Invalid = In Progress -- 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): In Progress 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1446286] [NEW] Exporting a deactivated image returns a generic task failure message
Public bug reported: Overview: When a user attempts to export a deactivated image, the operation fails as expected, but the message that is returned explaining why it failed is very generic. Steps to reproduce: 1) Import an image as user A 2) Deactivate the image as admin 3) Export the image as user A 4) Notice the export task fails, but with a generic error message Expected: A more detailed error message as to why the export task failed for a deactivated image Actual: A generic error message reading Unknown error occurred during import export 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/1446286 Title: Exporting a deactivated image returns a generic task failure message Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Overview: When a user attempts to export a deactivated image, the operation fails as expected, but the message that is returned explaining why it failed is very generic. Steps to reproduce: 1) Import an image as user A 2) Deactivate the image as admin 3) Export the image as user A 4) Notice the export task fails, but with a generic error message Expected: A more detailed error message as to why the export task failed for a deactivated image Actual: A generic error message reading Unknown error occurred during import export is returned. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1446286/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1445487] [NEW] Attempting to deactivate a queued image returns a 403
Public bug reported: 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 ** 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/1445487 Title: Attempting to deactivate a queued image returns a 403 Status in OpenStack Image Registry and Delivery Service (Glance): New 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1445608] [NEW] Deactivated images are not returned for list image requests
Public bug reported: Overview: After deactivating an image, the image owner can no longer see the image in a list images response. Steps to reproduce: 1) Create an image with user A 2) Deactivate the image with an admin 3) List all images, accounting for pagination as needed, with user A via: GET /images 4) Notice that the created (deactivated) image is not returned Expected: Deactivated images are returned in a list images response Actual: Deactivated images are not returned in a list images response ** 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/1445608 Title: Deactivated images are not returned for list image requests Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Overview: After deactivating an image, the image owner can no longer see the image in a list images response. Steps to reproduce: 1) Create an image with user A 2) Deactivate the image with an admin 3) List all images, accounting for pagination as needed, with user A via: GET /images 4) Notice that the created (deactivated) image is not returned Expected: Deactivated images are returned in a list images response Actual: Deactivated images are not returned in a list images response To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1445608/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1444033] Re: Attempting to list image, sorting the list by checksum returns 400 response
This was confused with another feature. This is not a bug and can be closed. ** 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/1444033 Title: Attempting to list image, sorting the list by checksum returns 400 response Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Overview: When attempting to list images, sorting the list by checksum, a 400 Bad Request response is returned. The message does not mention checksum as being an acceptable sort key even though it should be. Steps to reproduce: 1) List image, sorting the list by checksum via: GET /images?sort_key=checksum 2) Notice that a 400 Bad Request is returned and that the message does not mention checksum as being a valid sort key. Expected: A 200 response containing a list of images sorted by checksum Actual: A 400 response without a mention of checksum as a valid sort key To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1444033/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1444033] [NEW] Attempting to list image, sorting the list by checksum returns 400 response
Public bug reported: Overview: When attempting to list images, sorting the list by checksum, a 400 Bad Request response is returned. The message does not mention checksum as being an acceptable sort key even though it should be. Steps to reproduce: 1) List image, sorting the list by checksum via: GET /images?sort_key=checksum 2) Notice that a 400 Bad Request is returned and that the message does not mention checksum as being a valid sort key. Expected: A 200 response containing a list of images sorted by checksum Actual: A 400 response without a mention of checksum as a valid sort key ** 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/1444033 Title: Attempting to list image, sorting the list by checksum returns 400 response Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Overview: When attempting to list images, sorting the list by checksum, a 400 Bad Request response is returned. The message does not mention checksum as being an acceptable sort key even though it should be. Steps to reproduce: 1) List image, sorting the list by checksum via: GET /images?sort_key=checksum 2) Notice that a 400 Bad Request is returned and that the message does not mention checksum as being a valid sort key. Expected: A 200 response containing a list of images sorted by checksum Actual: A 400 response without a mention of checksum as a valid sort key To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1444033/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1444129] [NEW] Attempting to delete image member that does not exist returns 404 response, but with an incorrect message
Public bug reported: Overview: When attempting to delete image member that does not exist, a 404 response is returned, but with an incorrect message Steps to reproduce: 1) Create an image 2) Delete image member, passing 'dne' as member id via: DELETE /images/image_id/members/dne 3) Notice that a 404 response is returned and that the message reads 'Image image_id not found' Expected: A 404 response containing a message that reads 'Image member not found' Actual: A 404 response with a message that reads 'Image image_id not found' ** 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/1444129 Title: Attempting to delete image member that does not exist returns 404 response, but with an incorrect message Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Overview: When attempting to delete image member that does not exist, a 404 response is returned, but with an incorrect message Steps to reproduce: 1) Create an image 2) Delete image member, passing 'dne' as member id via: DELETE /images/image_id/members/dne 3) Notice that a 404 response is returned and that the message reads 'Image image_id not found' Expected: A 404 response containing a message that reads 'Image member not found' Actual: A 404 response with a message that reads 'Image image_id not found' To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1444129/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1440165] Re: List images passing tags as a sort_key returns a 500 response
Tested this with the latest version of Glance. This is no longer an issue and can be closed. ** Changed in: glance Status: Incomplete = 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/1440165 Title: List images passing tags as a sort_key returns a 500 response Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Overview: When attempting a list images request passing 'tags' as a sort_key takes a good amount of time to respond and then returns a 500 response. Steps to reproduce: 1) List images passing 'tags' as a sort_key via: curl -i 'endpoint/v2/images?sort_key=tags' -X GET -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: token 2) Notice that a 500 response is returned Expected: A list of images sorted by the 'tags' property value Actual: A 500 response is returned To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1440165/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1440120] Re: List images passing protected as a sort_key and a marker returns a 500 response
Tested with the latest version of Glance. This is no longer an issue. This bug can be closed. ** Changed in: glance Status: Incomplete = 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/1440120 Title: List images passing protected as a sort_key and a marker returns a 500 response Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Overview: When attempting a list images request passing 'protected' as a sort_key along with an image id as the marker returns a 500 response. Steps to reproduce: 1) List images passing 'protected' as a sort_key and an image id as the marker via: curl -i 'endpoint/v2/images?sort_key=protectedmarker=image id' -X GET -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: token 2) Notice that a 500 response is returned Expected: A list of images sorted by the 'protected' property value starting with the image passed in as the marker Actual: A 500 response is returned To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1440120/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1440170] Re: List images passing id as a sort_key returns an incorrectly ordered list of images
Tested this with the latest version of Glance. This no longer appears to be an issue and can be closed. ** Changed in: glance Status: Incomplete = 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/1440170 Title: List images passing id as a sort_key returns an incorrectly ordered list of images Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Overview: When attempting a list images request passing 'id' as a sort_key returns a list of images that are not in the correct order. Even when passing the sort_dir of asc or desc, the order is still incorrect. Steps to reproduce: 1) List images passing 'id' as a sort_key via: curl -i 'endpoint/v2/images?sort_key=id' -X GET -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: token 2) Notice that the list of images returned is not in the correct order 3) List images passing 'id' as a sort_key and asc or desc as the sort_dir via: curl -i 'endpoint/v2/images?sort_key=idsort_dir=asc' -X GET -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: token 4) Notice that the list of images returned is still not in the correct order Expected: A list of images correctly sorted by the 'id' property value Actual: A list of images is returned, but not correctly ordered, either asc or desc To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1440170/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1439827] Re: No results returned when listing images passing in the 'created_at' property as a filter
After further investigation, and to Kamil's point, using the created_at filter works when using the following formats: 2015-04-08T07:57:08Z 2015-04-08T07:57:08 2015-04-08-07:57:08 However, it does not work when using the following format: 2015-04-08-07:57:08+00:00 When using the updated_at image property as a filter, the above format does work. To be consistent, the same formats should work for both filters. ** Changed in: glance Status: Invalid = 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/1439827 Title: No results returned when listing images passing in the 'created_at' property as a filter Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Overview: When making the list images request, passing in a datetime for the created_at property, there are no results returned. Steps to reproduce: 1) Create an image, note the image's created_at property 2) Perform a list images request passing in the created_at property via GET /images?created_at=datetime 3) Notice no results are returned Expected: Return a list of images with the specified created_at datetime Actual: No results are returned To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1439827/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1443563] [NEW] Updating an image by removing 'id', 'file', 'location', 'schema', or 'self' returns a 409 response
Public bug reported:
Overview:
When a user attempts to update an image by removing 'id', 'file', 'location',
'schema', or 'self' as an image property, a 409 response is returned even
though every image has each of them by default.
Steps to reproduce:
1) Create an image
2) Update the image via PATCH /images/id passing '[{path: /id, value:
created_image_id, op: remove}]'
3) Notice that a 409 accepted response is returned
Expected:
A 403 response should be returned
Actual:
A 409 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/1443563
Title:
Updating an image by removing 'id', 'file', 'location', 'schema', or
'self' returns a 409 response
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
Overview:
When a user attempts to update an image by removing 'id', 'file', 'location',
'schema', or 'self' as an image property, a 409 response is returned even
though every image has each of them by default.
Steps to reproduce:
1) Create an image
2) Update the image via PATCH /images/id passing '[{path: /id, value:
created_image_id, op: remove}]'
3) Notice that a 409 accepted response is returned
Expected:
A 403 response should be returned
Actual:
A 409 response is returned
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1443563/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1443512] [NEW] Updating an image by adding 'visibility' returns a 200 response
Public bug reported:
Overview:
When a user attempts to update an image by adding 'visibility' as an image
property, a 200 response is returned.
Steps to reproduce:
1) Create an image
2) Update the image via PATCH /images/id passing '[{path: /visibility,
value: private, op: add}]'
3) Notice that a 200 accepted response is returned
Expected:
A 403 response should be returned
Actual:
A 200 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/1443512
Title:
Updating an image by adding 'visibility' returns a 200 response
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
Overview:
When a user attempts to update an image by adding 'visibility' as an image
property, a 200 response is returned.
Steps to reproduce:
1) Create an image
2) Update the image via PATCH /images/id passing '[{path: /visibility,
value: private, op: add}]'
3) Notice that a 200 accepted response is returned
Expected:
A 403 response should be returned
Actual:
A 200 response is returned
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1443512/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1442320] [NEW] Attempting to delete an image member from an image, passing a blank member_id returns a 404 response
Public bug reported: Overview: When attempting to delete an image member passing a blank member_id, a 404 (The resource could not be found) response is returned. Steps to reproduce: 1) Create a new image 2) Add an image member 3) Attempt to delete the image member passing '' for the member_id 4) Notice that a 404 response is returned Expected: Like the create image member response, if passing a blank member_id, a 400 (Member can't be empty) response should be returned. Actual: A 404 (The resource could not be found) 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/1442320 Title: Attempting to delete an image member from an image, passing a blank member_id returns a 404 response Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Overview: When attempting to delete an image member passing a blank member_id, a 404 (The resource could not be found) response is returned. Steps to reproduce: 1) Create a new image 2) Add an image member 3) Attempt to delete the image member passing '' for the member_id 4) Notice that a 404 response is returned Expected: Like the create image member response, if passing a blank member_id, a 400 (Member can't be empty) response should be returned. Actual: A 404 (The resource could not be found) response is returned To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1442320/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1441776] [NEW] Get image file passing image id without an image file returns a 204 response
Public bug reported: Overview: Attempting a GET /images/image_id/file returns a 204 response. At one point this returned a 404, but that does not appear to be the case anymore. Steps to reproduce: 1)Register a blank image via POST /images 2)Attempt a GET /images/image_id/file 3)Notice the response is a 204 Expected: A 404 response should be returned Actual: A 204 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/1441776 Title: Get image file passing image id without an image file returns a 204 response Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Overview: Attempting a GET /images/image_id/file returns a 204 response. At one point this returned a 404, but that does not appear to be the case anymore. Steps to reproduce: 1)Register a blank image via POST /images 2)Attempt a GET /images/image_id/file 3)Notice the response is a 204 Expected: A 404 response should be returned Actual: A 204 response is returned To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1441776/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1440163] [NEW] List images passing visibility as a sort_key returns a 400 response
Public bug reported: Overview: When attempting a list images request passing 'visibility' as a sort_key returns a 400 response. Steps to reproduce: 1) List images passing 'visibility' as a sort_key via: curl -i 'endpoint/v2/images?sort_key=visibility' -X GET -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: token 2) Notice that a 400 response is returned Expected: A list of images sorted by the 'visibility' property value Actual: A 400 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/1440163 Title: List images passing visibility as a sort_key returns a 400 response Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Overview: When attempting a list images request passing 'visibility' as a sort_key returns a 400 response. Steps to reproduce: 1) List images passing 'visibility' as a sort_key via: curl -i 'endpoint/v2/images?sort_key=visibility' -X GET -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: token 2) Notice that a 400 response is returned Expected: A list of images sorted by the 'visibility' property value Actual: A 400 response is returned To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1440163/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1440165] [NEW] List images passing tags as a sort_key returns a 500 response
Public bug reported: Overview: When attempting a list images request passing 'tags' as a sort_key takes a good amount of time to respond and then returns a 500 response. Steps to reproduce: 1) List images passing 'tags' as a sort_key via: curl -i 'endpoint/v2/images?sort_key=tags' -X GET -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: token 2) Notice that a 500 response is returned Expected: A list of images sorted by the 'tags' property value Actual: A 500 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/1440165 Title: List images passing tags as a sort_key returns a 500 response Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Overview: When attempting a list images request passing 'tags' as a sort_key takes a good amount of time to respond and then returns a 500 response. Steps to reproduce: 1) List images passing 'tags' as a sort_key via: curl -i 'endpoint/v2/images?sort_key=tags' -X GET -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: token 2) Notice that a 500 response is returned Expected: A list of images sorted by the 'tags' property value Actual: A 500 response is returned To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1440165/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1440120] [NEW] List images passing protected as a sort_key and a marker returns a 500 response
Public bug reported: Overview: When attempting a list images request passing 'protected' as a sort_key along with an image id as the marker returns a 500 response. Steps to reproduce: 1) List images passing 'protected' as a sort_key and an image id as the marker via: curl -i 'endpoint/v2/images?sort_key=protectedmarker=image id' -X GET -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: token 2) Notice that a 500 response is returned Expected: A list of images sorted by the 'protected' property value starting with the image passed in as the marker Actual: A 500 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/1440120 Title: List images passing protected as a sort_key and a marker returns a 500 response Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Overview: When attempting a list images request passing 'protected' as a sort_key along with an image id as the marker returns a 500 response. Steps to reproduce: 1) List images passing 'protected' as a sort_key and an image id as the marker via: curl -i 'endpoint/v2/images?sort_key=protectedmarker=image id' -X GET -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: token 2) Notice that a 500 response is returned Expected: A list of images sorted by the 'protected' property value starting with the image passed in as the marker Actual: A 500 response is returned To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1440120/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1440170] [NEW] List images passing id as a sort_key returns an incorrectly ordered list of images
Public bug reported: Overview: When attempting a list images request passing 'id' as a sort_key returns a list of images that are not in the correct order. Even when passing the sort_dir of asc or desc, the order is still incorrect. Steps to reproduce: 1) List images passing 'id' as a sort_key via: curl -i 'endpoint/v2/images?sort_key=id' -X GET -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: token 2) Notice that the list of images returned is not in the correct order 3) List images passing 'id' as a sort_key and asc or desc as the sort_dir via: curl -i 'endpoint/v2/images?sort_key=idsort_dir=asc' -X GET -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: token 4) Notice that the list of images returned is still not in the correct order Expected: A list of images correctly sorted by the 'id' property value Actual: A list of images is returned, but not correctly ordered, either asc or desc ** 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/1440170 Title: List images passing id as a sort_key returns an incorrectly ordered list of images Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Overview: When attempting a list images request passing 'id' as a sort_key returns a list of images that are not in the correct order. Even when passing the sort_dir of asc or desc, the order is still incorrect. Steps to reproduce: 1) List images passing 'id' as a sort_key via: curl -i 'endpoint/v2/images?sort_key=id' -X GET -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: token 2) Notice that the list of images returned is not in the correct order 3) List images passing 'id' as a sort_key and asc or desc as the sort_dir via: curl -i 'endpoint/v2/images?sort_key=idsort_dir=asc' -X GET -H Content-Type: application/json -H Accept: application/json -H X-Auth-Token: token 4) Notice that the list of images returned is still not in the correct order Expected: A list of images correctly sorted by the 'id' property value Actual: A list of images is returned, but not correctly ordered, either asc or desc To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1440170/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1439827] [NEW] No results returned when listing images passing in the 'created_at' property as a filter
Public bug reported: Overview: When making the list images request, passing in a datetime for the created_at property, there are no results returned. Steps to reproduce: 1) Create an image, note the image's created_at property 2) Perform a list images request passing in the created_at property via GET /images?created_at=datetime 3) Notice no results are returned Expected: Return a list of images with the specified created_at datetime Actual: No results are 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/1439827 Title: No results returned when listing images passing in the 'created_at' property as a filter Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Overview: When making the list images request, passing in a datetime for the created_at property, there are no results returned. Steps to reproduce: 1) Create an image, note the image's created_at property 2) Perform a list images request passing in the created_at property via GET /images?created_at=datetime 3) Notice no results are returned Expected: Return a list of images with the specified created_at datetime Actual: No results are returned To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1439827/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1439808] [NEW] Updating an image by adding 'id' returns a 200 response
Public bug reported:
Overview:
When a user attempts to update an image by adding 'id' as an image property, a
200 response is returned.
Steps to reproduce:
1) Create an image
2) Update the image via PATCH /images/id passing '[{path: /id, value:
----, op: add}]'
3) Notice that a 200 accepted response is returned even though the image does
not appear to be updated
Expected:
A 403 or 409 response should be returned
Actual:
A 200 response is returned and the image does not appear to be updated
** 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/1439808
Title:
Updating an image by adding 'id' returns a 200 response
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
Overview:
When a user attempts to update an image by adding 'id' as an image property,
a 200 response is returned.
Steps to reproduce:
1) Create an image
2) Update the image via PATCH /images/id passing '[{path: /id, value:
----, op: add}]'
3) Notice that a 200 accepted response is returned even though the image does
not appear to be updated
Expected:
A 403 or 409 response should be returned
Actual:
A 200 response is returned and the image does not appear to be updated
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1439808/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1438826] [NEW] Able to update an image passing id, file, location, schema, and self
Public bug reported: Overview: A user is able to update an image via PATCH /images/image_id when passing in id, file, location, schema, and self. However, these are restricted image properties. Steps to reproduce: 1) Create an image 2) Update the image via PATCH /images/image_id and pass in id, file, location, schema, and self 2) Notice the request is accepted and the image is updated Expected: Because these properties are restricted, when attempting to update an image and they appear to be properties that should be automatically generated, the request should not be allowed. Actual: The request is accepted and the image is updated ** 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/1438826 Title: Able to update an image passing id, file, location, schema, and self Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Overview: A user is able to update an image via PATCH /images/image_id when passing in id, file, location, schema, and self. However, these are restricted image properties. Steps to reproduce: 1) Create an image 2) Update the image via PATCH /images/image_id and pass in id, file, location, schema, and self 2) Notice the request is accepted and the image is updated Expected: Because these properties are restricted, when attempting to update an image and they appear to be properties that should be automatically generated, the request should not be allowed. Actual: The request is accepted and the image is updated To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1438826/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
