Some configurations on the compute node is not right in a multinode devstack setup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Fix Released
|
Low
|
Tal Kain |
Bug Description
I setup a two node devstack environment. On the controller node, the localrc is as below:
RECLONE=yes
disable_service n-net
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta
enable_service quantum
enable_service tempest
FLOATING_
FIXED_RANGE=
FIXED_NETWORK_
FLAT_INTERFACE=eth0
ADMIN_PASSWORD=
MYSQL_PASSWORD=
RABBIT_
SERVICE_
SERVICE_
HOST_IP=192.168.3.2
MULTI_HOST=True
LOGFILE=
The localrc at another compute node is as below:
RECLONE=yes
HOST_IP=192.168.3.8
FLAT_INTERFACE=eth0
FIXED_RANGE=
FIXED_NETWORK_
FLOATING_
MULTI_HOST=1
ADMIN_PASSWORD=
MYSQL_PASSWORD=
RABBIT_
SERVICE_
SERVICE_
MYSQL_HOST=
RABBIT_
Q_HOST=192.168.3.2
GLANCE_
ENABLED_
After I ran $./stack.sh on both the controller node and the compute node. The compute node has the following errors on Cinder.
File "/usr/local/
Then I checked the /etc/cinder/
When I tried to boot a server using $nova boot --image ** --flavor 1 --availability-zone nova:comp test1, the compute node has the following error on Nova:
TRACE nova.network.
Then I checked the /etc/nova/nova.conf on the compute node and found that quantum_
It seems to me that the script might not correctly update these two configuration files on the compute nodes.
Changed in devstack: | |
importance: | Undecided → Low |
Changed in devstack: | |
assignee: | nobody → Tal Kain (talkain) |
status: | New → In Progress |
Hey,
I had the same issue and I just found out how to fix it.
First: 78bafaafe7e8b3b 5de733971c "Deprecate DATABASE_TYPE and use_database" - changed the way devstack configures the database you use. If you look at the current "ENABLED_SERVICES" you will see "mysql" is configured in it. When you re-configured it as http:// devstack. org/guides/ multinode- lab.html suggest, you will disable the compute node's database.
afc29fe5f210a8e
So just add mysql to the end of your ENABLED_SERVICES line.
Second: 5f732de9a39cc54 bedd95bd6f' s changes created a bug.
As far as I can see 7e79d9139f931e4
This patch fixes it:
From 4a9eb2582d704f5 f4ebb6532eb0436 285d3de0fe Mon Sep 17 00:00:00 2001 connection_ url that
From: Tal Kain <email address hidden>
Date: Mon, 22 Apr 2013 17:50:27 +0300
Subject: [PATCH] lib/database: Fixed a bug in database_
was created by d95bd6f's changes
7e79d9139f931e4 5f732de9a39cc54 bedd95bd6f' s changes simplified the usage of database_ connection_ url_mysql and database_ connection_ url_postgresql without making the proper changes to database_ connection_ url.
Signed-off-by: Tal Kain <email address hidden>
---
lib/database | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/lib/database b/lib/database database_ $DATABASE_ TYPE
index e63d5e2..08e360f 100644
--- a/lib/database
+++ b/lib/database
@@ -110,13 +110,11 @@ function configure_database {
configure_
}
-# Generate an SQLAlchemy connection URL and store it in a variable connection_ url { connection_ url_$DATABASE_ TYPE $var $db connection_ url_$DATABASE_ TYPE $db
-# $1 The variable name in which to store the connection URL
-# $2 The name of the database
+# Generate an SQLAlchemy connection URL and output it using echo
+# $1 The name of the database
function database_
- local var=$1
- local db=$2
- database_
+ local db=$1
+ database_
}
--
1.7.9.5
Good luck!
Tal Kain.