ec2 api entry point for DescribeImages shows only public

[Scott Moser]

http://docs.amazonwebservices.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html

It seems that Ec2 api DescribeImages is not showing any private images.

# publish a bogus image
$ rm -f my.img; truncate --size 100k my.img;
$ cloud-publish-image amd64 my.img my-junk
ami-0000017c my-junk/my.img.manifest.xml

# it doesn't show up in DescribeImages
$ euca-describe-images | grep ami-0000017c

# but it does if you make it public
$ euca-modify-image-attribute -l -a all ami-0000017c
IMAGE ami-0000017c
$ euca-describe-images | grep ami-0000017c
IMAGE ami-0000017c my-junk/my.img.manifest.xml None available public x86_64 machine instance-store

# remove public again, and try explicitly requesting owner=self
$ euca-modify-image-attribute -l -r all ami-0000017c
IMAGE ami-0000017c
$ euca-describe-images -o self | grep ami-0000017c

# show that with public, that *does* work
$ euca-modify-image-attribute -l -a all ami-0000017c
IMAGE ami-0000017c
$ euca-describe-images -o self | grep ami-0000017c
IMAGE ami-0000017c my-junk/my.img.manifest.xml None available public x86_64 machine instance-store

# show that in both cases, it shows up via nova api
$ euca-modify-image-attribute -l -r all ami-0000017c
IMAGE ami-0000017c
$ xnova image-list | grep my-junk
| 36880450-3e62-449b-8470-a70ad8a3a153 | my-junk/my.img | ACTIVE | |

$ euca-modify-image-attribute -l -a all ami-0000017c
IMAGE ami-0000017c
$ xnova image-list | grep my-junk
| 36880450-3e62-449b-8470-a70ad8a3a153 | my-junk/my.img | ACTIVE | |

[Scott Moser (smoser)]

I saw this when running against a private openstack deployment.
It does not reproduce in a devstack instance I just started with nova at:

commit 8bca678798b251d81a360d8d3ac08495b1279dc1
Merge: f495b95 b68e63b
Author: Jenkins <email address hidden>
Date: Fri Dec 7 08:30:08 2012 +0000

    Merge "Sync RPC logging-related bits from oslo"

and glance at:
commit 3968b7cc8bfa8cb8118e63944363ca0b3057e95c
Author: Attila Fazekas <email address hidden>
Date: Fri Nov 30 23:49:52 2012 +0100

    Allow newer boto library versions

    Change the boto dependency specification in pip-requires to just 'boto'
    without version restriction, as it was before the build issue.

    Change-Id: Iff484f1e40fe103879ff11a611c0691486288be6

[Scott Moser (smoser)]

I've opened a ubuntu/nova task for this. It is reported to me that the openstack cluster that I was working against (known as canonistack) is running folsom 2012.2-0ubuntu3~cloud0.

we probalby need more details there, but want to follow up on this.