SOLVED ! (the problem, as usual, was between chair and keyboard)
I put some nice log in "configure_db" particularly the options dict and see that the sql connection use sqlite:// The step leading to the problem : checkout/update quantum repo, copy the conf file to /etc/quantum but *keep the original (not configure to your need) in xxx/quantum/etc/ dir* => quantum will load them instead of /etc/quantum even if you set the '--config-file' option in the command line. I believe it's an existing bug. I should have taken more attention in reading devstack code where they move the file, not copy it...
Salvatore, thanks for your help. Now, back to business ;-) --- Nicolas On Thu Jul 26 07:06:59 2012, Salvatore Orlando wrote:
I admin I have never seen anything like this. The issue must then be either in configure_db or register_models, both in db/api.py, even if I would have expected to see "Database Registration Exception" in the logs. However, I cannot say what's the root cause for the issue - Quantum, sqlAlchemy, or something else in your environment. I know this sounds odd, but if you can instrument configure_db code to see which paths are taken into that routine that might help us understand a little bit better what's happening in your environment, and maybe file a bug for Quantum if required. I am on the #openstack-dev IRC channel, my nick is salv-orlando. Feel free to ping me. Salvatore
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
