glance-manage does not read configuration correctly

Bug #1070630 reported by Sina Sadeghi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glance (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Hi guys,

I have been utilising the glance Folsom packages provided in the Ubuntu Cloud Archive repo. On installation of a new glance server using a glance-api.conf and glance-registry.conf which point to mysql rather than the default sqlite backend, I am coming up across the following issue:

When running glance-manage db-sync the program doesn't seem to import the sql_connection line from either glance-api.conf or glance-registry.conf and simply does the db-sync against the /var/lib/glance/glance.sqlite file. This means the DB schema and db-sync itself are not created and performed on the mysql db!

This isn't a misconfiguration issue or connection problem, as if I modify the api.py code to set autocreate tables = True, then when starting glance-api it correctly reads the configuration, connects to mysql (not sqlite!) and creates the DB schema and performs a db-sync.

Please rectify, and push the fix to Ubuntu Cloud Archive ASAP.

Sina Sadeghi (sina-sa)
no longer affects: ubuntu
Revision history for this message
Sina Sadeghi (sina-sa) wrote :

I re-deployed a fresh Ubuntu 12.04.1 server and was no longer affected by this issue. Closing.

Chuck Short (zulcss)
Changed in glance (Ubuntu):
status: New → Won't Fix
Brian Waldon (bcwaldon)
no longer affects: glance
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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