Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lack of explanation in image-related 404 error responses #31

Open
saxtouri opened this issue Mar 26, 2014 · 0 comments
Open

Lack of explanation in image-related 404 error responses #31

saxtouri opened this issue Mar 26, 2014 · 0 comments

Comments

@saxtouri
Copy link
Contributor

When requesting details for a non-existing image trough the API, the 404 error lacks an explanation.

This is not the case with other cyclades 404 errors, e.g. a server-related 404 will contain something like "server 9999 not found" and the same holds for networks, flavors, ips, etc.

To reproduce the issue:

Assume the image id 9999 does not exist.
Try the following:

$ kamaki image info 9999 -v -o log_data=on
> HEAD https://example.com/image/1.0/images/9999
> [...]
< 404 NOT FOUND
(empty body)

Similarly with compute/image API:

$ kamaki imagecompute info 9999 -v -o log_data=on
> GET https://example.com/compute/v2.0/images/9999
> [...]
< 404 NOT FOUND
< {"itemNotFound": {"message": "", "code": 404, "details": ""}}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant