From ed6e1d0996a910eca42a202f17dfeee53d250c00 Mon Sep 17 00:00:00 2001 From: Lance Bragstad Date: Wed, 1 Aug 2018 18:03:44 +0000 Subject: [PATCH] Set transport_url in proper keystone config section The RPC transport_url for keystone was being set in the DEFAULT section, even though keystone doesn't do anything with it. Instead, keystone leans on the [oslo_messaging_notification] section from oslo.messaging to register the transport_url option. This change sets the transport_url in the proper section instead of using the DEFAULT section. Change-Id: I11590d0175da7ea310d5529f2d7c0bf8d7fb25b3 --- lib/keystone | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/keystone b/lib/keystone index 57cb24d4cb..02e28222b7 100644 --- a/lib/keystone +++ b/lib/keystone @@ -217,7 +217,7 @@ function configure_keystone { iniset $KEYSTONE_CONF cache backend "dogpile.cache.memcached" iniset $KEYSTONE_CONF cache memcache_servers localhost:11211 - iniset_rpc_backend keystone $KEYSTONE_CONF + iniset_rpc_backend keystone $KEYSTONE_CONF oslo_messaging_notifications local service_port=$KEYSTONE_SERVICE_PORT local auth_port=$KEYSTONE_AUTH_PORT