Nova image API requires tenant_id in URI

Bug #1350249 reported by Ma, Tianxiao
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-api-site
Fix Released
Medium
Atsushi SAKAI

Bug Description

Please look at API listed in http://docs.openstack.org/api/openstack-compute/2/content/Images-d1e4427.html

It lists a group of APIs to list/show/delete images.

GET /v2/images/detail​{?changes-since,​server,​name,​status,​marker,​limit,​type}
Lists all details for available images.

GET /v2/images/{image_id}
Gets details for a specified image.

DELETE /v2/images/{image_id}
Deletes a specified image.

All of them are missing tenant_id, correct URI should be v2/{tenant_id}/image/...
GET /{tenant_id}/v2/images/detail​{?changes-since,​server,​name,​status,​marker,​limit,​type}
GET /v2/{tenant_id}/images/{image_id}
DELETE /v2/{tenant_id}/images/{image_id}

Looks like a mistake in documentation.

Please confirm it, thank you.

Tags: nova
Revision history for this message
Anne Gentle (annegentle) wrote :
Changed in openstack-api-site:
status: New → Confirmed
importance: Undecided → Medium
Atsushi SAKAI (sakaia)
Changed in openstack-api-site:
assignee: nobody → Atsushi SAKAI (sakaia)
Revision history for this message
Atsushi SAKAI (sakaia) wrote :

Is this current REST url correct? it is written as follows.

GET​ {tenant_id}​/images
http://developer.openstack.org/api-ref-compute-v2.html#compute_images

no need to write "/v2/"?
it seems different issue not "{tenant_id}"

Atsushi SAKAI (sakaia)
Changed in openstack-api-site:
assignee: Atsushi SAKAI (sakaia) → nobody
Atsushi SAKAI (sakaia)
tags: added: nova
Revision history for this message
Atsushi SAKAI (sakaia) wrote :

It seems already fixed.

Revision history for this message
Diane Fleming (diane-fleming) wrote :

Fixed through another patch.

Changed in openstack-api-site:
status: Confirmed → Fix Released
milestone: none → liberty
assignee: nobody → Atsushi SAKAI (sakaia)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.