Glance

'glance index' and 'glance details' empty

Bug #894741 reported by Nicolae Paladi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Invalid
Undecided
Unassigned

Bug Description

I have a situation very similar to the one described in https://bugs.launchpad.net/nova/+bug/808990; log outputs are also very similary.

however, I suspect in this case there is an issue with Glance, since running

glance details
glance index

does not return anything.

some more background:

root@cloud-controller-node:~# euca-describe-images

produces:

IMAGE ami-00000007 test_2/6.manifest.xml available private i386 machine
IMAGE ami-00000006 test_2/maverick-server-uec-amd64.img.manifest.xml available private i386 machine aki-00000005
IMAGE aki-00000005 test_2/maverick-server-uec-amd64-vmlinuz-virtual.manifest.xml available private i386 kernel
IMAGE ami-00000004 test_bucket/maverick-server-uec-amd64.img.manifest.xml available private i386 machine aki-00000003
IMAGE aki-00000003 test_bucket/maverick-server-uec-amd64-vmlinuz-virtual.manifest.xml available private i386 kernel
IMAGE ami-00000002 dub-bucket/maverick-server-uec-amd64.img.manifest.xml available private i386 machine aki-00000001
IMAGE aki-00000001 dub-bucket/maverick-server-uec-amd64-vmlinuz-virtual.manifest.xml available private i386 kernel

root@cloud-controller-node:~# euca-describe-instances

poduces:

RESERVATION r-mjdn2mqd dubproject default
INSTANCE i-00000025 ami-00000006 192.168.0.7 192.168.0.7 pending test (dubproject, cloud-compute-node) 0 m1.tiny 2011-11-25T09:52:06Z nova aki-00000005 ami-00000000
RESERVATION r-vsgr0sbi dubproject default
INSTANCE i-00000013 ami-00000002 192.168.0.2 192.168.0.2 running test (dubproject, cloud-controller-node) 0 m1.tiny 2011-11-16T13:05:46Z nova aki-00000001 ami-00000000
RESERVATION r-jnr82uaj dubproject default
INSTANCE i-00000022 ami-00000006 192.168.0.3 192.168.0.3 running test1 (dubproject, cloud-controller-node) 0 m1.tiny 2011-11-24T16:26:54Z nova aki-00000005 ami-00000000
RESERVATION r-z0z5svok dubproject default
INSTANCE i-0000001b ami-00000006 192.168.0.8 192.168.0.8 pending test1 (dubproject, cloud-compute-node) 0 m1.tiny 2011-11-24T15:17:19Z nova aki-00000005 ami-00000000
RESERVATION r-04m9yh54 dubproject default
INSTANCE i-00000024 ami-00000006 192.168.0.6 192.168.0.6 pending test1 (dubproject, cloud-compute-node) 0 m1.tiny 2011-11-24T16:55:12Z nova aki-00000005 ami-00000000
RESERVATION r-xsi80yt9 dubproject default
INSTANCE i-00000023 ami-00000006 192.168.0.5 192.168.0.5 pending test1 (dubproject, cloud-compute-node) 0 m1.tiny 2011-11-24T16:47:22Z nova aki-00000005 ami-00000000
RESERVATION r-agooawpv dubproject default
INSTANCE i-00000015 ami-00000004 192.168.0.4 192.168.0.4 running test (dubproject, cloud-controller-node) 0 m1.tiny 2011-11-24T13:46:15Z nova aki-00000003 ami-00000000

However, when running

curl:[controller-host]:9191 in the compute node

I get: {"images": []} (as opposed the description in https://bugs.launchpad.net/nova/+bug/808990/comments/2)

same out put for curl:[controller-host]:9292/v1/images

output of curl:9292 is

{"versions": [{"status": "CURRENT", "id": "v1.1", "links": [{"href": "http://[controller-host]:9292/v1/", "rel": "self"}]}, {"status": "SUPPORTED", "id": "v1.0", "links": [{"href": "http://[controller-host]:9292/v1/", "rel": "self"}]}]}

Revision history for this message
Nicolae Paladi (n-paladi) wrote :

Forgot to mention, version is:

glance 2011.3

Revision history for this message
Jay Pipes (jaypipes) wrote :

Hi!

Please pastebin your conf files (api and registry) and please pastebin your API log file contents.

Remember to remove any sensitive security credentials!

Thanks,
-jay

Revision history for this message
Nicolae Paladi (n-paladi) wrote :

Here are the links to

glance-api.conf: http://pastebin.com/kyaTGF3x

and

glance-registry.conf: http://pastebin.com/PNBfGBMU

Some token values were replaced by "xxxxxxxxxxxxx"

Revision history for this message
Jay Pipes (jaypipes) wrote :

Hi! Would you also please pastebin your glance-api log file? Thanks for your patience!
-jay

Revision history for this message
Nicolae Paladi (n-paladi) wrote :

Hi!

Sure, here's the url:
http://pastebin.com/U27AJQEU

Note that the IP of the cloud controller (where glance in installed) has been replaced by '[hostIP]'

/nico

Revision history for this message
Jay Pipes (jaypipes) wrote :

OK, my guess is that these images were all added before you enabled authentication in the glance-api and glance-registry pipelines. And so, what is happening when you do glance index or glance details is that Glance is looking for all the images that you own. But your user doesn't actually own the images, since authentication was not enabled when you originally added the images using euca-bundle-image/uec-publish-tarball etc. I believe this is the case because all of the images showing in euca-describe-images are marked private...

Is that correct? If so, you will need to manually update the owner property of the images to your Nova project ID...

To do so, you can directly edit the Glance registry database and just UPDATE images SET owner = <YOUR_PROJECT_ID> or you can use the glance tool like so:

glance update <IMAGE_ID> owner=<YOUR_PROJECT_ID>

I *think* the latter should work... but let me know if it does not...

-jay

Revision history for this message
Nicolae Paladi (n-paladi) wrote :

Hi Jay,

you're right, the suggested solution works and the instances are now running on the cloud compute node (except that I can't ping or ssh to them but that's a different issue I guess).

Thanks for the help!
cheers,
/nico.

Revision history for this message
Jay Pipes (jaypipes) wrote :

No problem, Nico! Marking this as Invalid.

Thanks!
-jay

Changed in glance:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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