Using the latest release of Glance Grizzly (git 2d9b3f1) on Fedora 17.
It appears that Glance can return a 404 message which contains the backend Swift store password *when* there are errors obtaining the image from Swift.
Example:
[root@nova1 image]# glance image-download foo Request returned failure status. 404 Not Found Swift could not find image at uri swift+http://admin%3Aadmin:AABBCC112233@127.0.0.1:5000/v2.0/glance/b0bd4daf-0cef-448e-b5f2-3033d0f5a73a (HTTP 404)
----
The above could happen for *any* user that can run Glance commands.
A simple way to replicate this is to do something like this:
1) Setup Glance using Swift as a backend (single tenant mode).
2) Remove or block an image from the swift account where images are stored.
3) Attempt to download the same image (which you removed from Swift) from Glance.
---
The root cause of the issue appears to be that the Swift store raises exception with the backend location in them.
Using the latest release of Glance Grizzly (git 2d9b3f1) on Fedora 17.
It appears that Glance can return a 404 message which contains the backend Swift store password *when* there are errors obtaining the image from Swift.
Example:
[root@nova1 image]# glance image-download foo admin%3Aadmin: AABBCC112233@ 127.0.0. 1:5000/ v2.0/glance/ b0bd4daf- 0cef-448e- b5f2-3033d0f5a7 3a
Request returned failure status.
404 Not Found
Swift could not find image at uri swift+http://
(HTTP 404)
----
The above could happen for *any* user that can run Glance commands.
A simple way to replicate this is to do something like this:
1) Setup Glance using Swift as a backend (single tenant mode).
2) Remove or block an image from the swift account where images are stored.
3) Attempt to download the same image (which you removed from Swift) from Glance.
---
The root cause of the issue appears to be that the Swift store raises exception with the backend location in them.