Browse code
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
Lance Bragstad authored on 2018/08/02 03:03:44Showing 1 changed files
| ... | ... |
@@ -217,7 +217,7 @@ function configure_keystone {
|
| 217 | 217 |
iniset $KEYSTONE_CONF cache backend "dogpile.cache.memcached" |
| 218 | 218 |
iniset $KEYSTONE_CONF cache memcache_servers localhost:11211 |
| 219 | 219 |
|
| 220 |
- iniset_rpc_backend keystone $KEYSTONE_CONF |
|
| 220 |
+ iniset_rpc_backend keystone $KEYSTONE_CONF oslo_messaging_notifications |
|
| 221 | 221 |
|
| 222 | 222 |
local service_port=$KEYSTONE_SERVICE_PORT |
| 223 | 223 |
local auth_port=$KEYSTONE_AUTH_PORT |