Bug 847785
Summary: | Quantum installation scripts for linux bridge do not set correct database parameters in the configuration file | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Gary Kotton <gkotton> |
Component: | openstack-quantum | Assignee: | Alan Pevec <apevec> |
Status: | CLOSED ERRATA | QA Contact: | Jaroslav Henner <jhenner> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 1.0 (Essex) | CC: | jhenner, markmc, pbrady |
Target Milestone: | ga | ||
Target Release: | 1.0 Essex | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-quantum-2012.1-8.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-10-16 15:45:16 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Gary Kotton
2012-08-13 14:36:41 UTC
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 |