Comment 2 for bug 966079

Hi Christian,

The in-memory database should be used only for running the tests.

As for the MySQL DB conf, I am guessing that you might have not created the quantum DB, or the right privileges are not being set on the tables. I am paraphrasing the following from the README file; if you follow these steps, I think this error will go away (note the database name suggested here is quantum_linux_bridge, and if you do use that name, make sure that you have the same name in the agent's conf file; both, the Quantum service and the agent have to refer to the same DB):

# -- Database config.

(Note: The plugin ships with a default SQLite in-memory database configuration,
 and can be used to run tests without performing the suggested DB config below.)

The Linux Bridge quantum plugin requires access to a mysql database in order
to store configuration and mappings that will be used by the agent. Here is
how to set up the database on the host that you will be running the quantum
service on.

MySQL should be installed on the host, and all plugins and clients
must be configured with access to the database.

To prep mysql, run:

$ mysql -u root -p -e "create database quantum_linux_bridge"

# log in to mysql service
$ mysql -u root -p
# The Linux Bridge Quantum agent running on each compute node must be able to
# make a mysql connection back to the main database server.
mysql> GRANT USAGE ON *.* to root@'yourremotehost' IDENTIFIED BY 'newpassword';
# force update of authorization changes
mysql> FLUSH PRIVILEGES;

(Note: If the remote connection fails to MySQL, you might need to add the IP address,
 and/or fully-qualified hostname, and/or unqualified hostname in the above GRANT sql
 command. Also, you might need to specify "ALL" instead of "USAGE".)

Thanks,
~Sumit.