Public bug reported:
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.
** Affects: glance
Importance: Undecided
Status: New
** Affects: ubuntu
Importance: Undecided
Status: New
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070630
Title:
glance-manage does not read configuration correctly
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1070630/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
