Description of problem: When using the installation scripts quantum-node-setup and quantum-server-setup the quantum agent and the quantum service are unable to communicate with the database. Version-Release number of selected component (if applicable): RH Essex How reproducible: Every time. Steps to Reproduce: 1. Install quantum service package (openstack-quantum) 2. Install quntum linux bridge plugin (openstack-quantum-linuxbridge) 3. Run quantum-node-setup and quantum-server-setup. In the linux bridge plugin file. In the file /etc/quantum/plugins/linuxbridge/linuxbridge_conf.ini the following entry does not appear sql_connection Actual results: Quantum agent is unable to communicate with quantum server Quantum server will lose all data after retsarting Expected results: It should all work :) Additional info:
The problem has already been addressed in Fedora:- https://koji.fedoraproject.org/koji/buildinfo?buildID=347429 Please note that the problem only occurs when the packging utility scripts are used for the deployment. This is not related to the Quantum code just to the configuration.
[root@quantum-server ~]# grep sql_conn /etc/quantum/plugins/linuxbridge/linuxbridge_conf.ini # sql_connection = mysql://root:nova.0.1:3306/quantum_linux_bridge sql_connection = mysql://quantum:quantum.../quantum_linux_bridge [root@quantum-node ~]# grep sql_conn /etc/quantum/plugins/linuxbridge/linuxbridge_conf.ini # sql_connection = mysql://root:nova.0.1:3306/quantum_linux_bridge sql_connection = mysql://quantum:quantum/quantum_linux_bridge ... so far so good. I'm going to test whether all is talking together.
I managed to get. [root@quantum-node ~]# brctl show bridge name bridge id STP enabled interfaces brqf827be69-e6 8000.52540055f210 no eth1.1001 tap0fbefbb8-82 VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-1377.html