Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I've discovered this in the glance-registry.log

2012-04-17 14:12:23 3978 ERROR [glance.registry.db.api] (ProgrammingError) (1146, "Table 'glance.images' doesn't exist") 'SELECT images.created_at AS images_created_at, images.updated_at AS images_updated_at, images.deleted_at AS images_deleted_at, images.deleted AS images_deleted, AS images_id, AS images_name, images.disk_format AS images_disk_format, images.container_format AS images_container_format, images.size AS images_size, images.status AS images_status, images.is_public AS images_is_public, images.location AS images_location, images.checksum AS images_checksum, images.min_disk AS images_min_disk, images.min_ram AS images_min_ram, images.owner AS images_owner, images.protected AS images_protected \nFROM images \n LIMIT %s' (1,) 2012-04-17 14:12:23 3978 ERROR [glance.registry.db.api] Could not ensure database connection and consistency. Ensure database configuration and permissions are correct and database has been migrated since last upgrade by running 'glance-manage db_sync'

I use the glance-manage db_sync command and I still get the error. The database does have something in it, although I don't see the glance.images table. I'm missing a configuration step I think.

-----Original Message----- From: Mize, Donald Sent: Tuesday, April 17, 2012 11:35 AM To: '' Subject: RE: [Question #193860]: problem verifying glance

keystone 2012.1-0ubuntu1

glance 2012.1-0ubuntu2


Default minimal pipeline

[pipeline:glance-registry] pipeline = context registryapp

Use the following pipeline for keystone auth

i.e. in glance-registry.conf:


flavor = keystone

# [pipeline:glance-registry-keystone] pipeline = authtoken context registryapp

[app:registryapp] paste.app_factory = glance.common.wsgi:app_factory glance.app_factory = glance.registry.api.v1:API

[filter:context] context_class = glance.registry.context.RequestContext paste.filter_factory = glance.common.wsgi:filter_factory glance.filter_factory = glance.common.context:ContextMiddleware

[filter:authtoken] paste.filter_factory = keystone.middleware.auth_token:filter_factory service_protocol = http service_host = service_port = 5000 auth_host = auth_port = 35357 auth_protocol = http auth_uri = admin_tenant_name = service admin_user = glance

admin_password = glance



flavor = keystone



flavor = keystone

There was no paste deploy in glance-api-paste.ini, the install and deploy document didn't say anything about it.

root@xnode9:/etc/glance# export | grep OS declare -x LESSCLOSE="/usr/bin/lesspipe %s %s"

root@xnode9:/etc/glance# keystone --token ADMIN --endpoint endpoint-list +----------------------------------+-----------+------------------------------+------------------------------+------------------------------+ | id | region | publicurl | internalurl | adminurl | +----------------------------------+-----------+------------------------------+------------------------------+------------------------------+ | 5f780a73764f4c828b57b91366cb75b9 | RegionOne | | | | | 653a2bf1b3b04985b9d140b9626f8797 | RegionOne | | | | | 78186b626031484f8dab4de08753a7b5 | RegionOne | | | | | a1c8ef113861443a8a5bac01ff44bb5e | RegionOne | | | | +----------------------------------+-----------+------------------------------+------------------------------+------------------------------+

Thanks! Don

-----Original Message----- From: [] On Behalf Of smallma Sent: Tuesday, April 17, 2012 4:11 AM To: Mize, Donald Subject: Re: [Question #193860]: problem verifying glance

Your question #193860 on Glance changed:

Status: Open => Needs information

smallma requested more information: Can you paste the following information?

  1. keystone and glance version
  2. glance-registry-paste.ini, [paste_deploy] in glance-registry.conf glance-api-paste.ini and [paste_deploy] in glance-api.conf
  3. export | grep OS in client node
  4. endpoint-list in keystone



-- To answer this request for more information, you can either reply to this email or enter your reply at the following page:

You received this question notification because you asked the question.