workaround: add ending '/' to oslo-messaging transport url

oslo-messaging 9.0.1 requires the ending '/' to properly
use default virtual host '/'. Otherwise, it attempts to connect to
virtual host 'None' and gets refused.

Related-Bug: 1798241

Change-Id: I318a0496f9a71c80674b114b5c6f898cf080c058
This commit is contained in:
Eric K 2018-10-16 14:35:19 -07:00 committed by Eric Kao
parent 874ff3823f
commit 993f9b301e
3 changed files with 3 additions and 1 deletions

View File

@ -5,6 +5,7 @@ datasource_sync_period = 5
debug = True
replicated_policy_engine = True
encryption_key_path = 'congress/tests/etc/keys'
transport_url = rabbit:///
[database]
# connection = mysql+pymysql://root:password@127.0.0.1/congress?charset=utf8

View File

@ -5,6 +5,7 @@ datasource_sync_period = 5
debug = True
replicated_policy_engine = True
encryption_key_path = 'congress/tests/etc/keys'
transport_url = rabbit:///
[database]
# connection = mysql+pymysql://root:password@127.0.0.1/congress?charset=utf8

View File

@ -59,7 +59,7 @@ function configure_congress {
iniset $CONGRESS_CONF DEFAULT auth_strategy $CONGRESS_AUTH_STRATEGY
iniset $CONGRESS_CONF DEFAULT datasource_sync_period 30
iniset $CONGRESS_CONF DEFAULT replicated_policy_engine "$CONGRESS_REPLICATED"
iniset $CONGRESS_CONF DEFAULT transport_url rabbit://$RABBIT_USERID:$RABBIT_PASSWORD@$RABBIT_HOST:5672
iniset $CONGRESS_CONF DEFAULT transport_url rabbit://$RABBIT_USERID:$RABBIT_PASSWORD@$RABBIT_HOST:5672/
iniset $CONGRESS_CONF database connection `database_connection_url $CONGRESS_DB_NAME`
_congress_setup_keystone $CONGRESS_CONF keystone_authtoken