From 4440da85637aa8239f24bd4f23a9a8e1ac2d0b8d Mon Sep 17 00:00:00 2001 From: Adam Young Date: Wed, 26 Oct 2016 11:40:08 +0200 Subject: [PATCH] Unset admin_project config options for Keystone Until the policy changes land for Nova, Glance, etc, this value is not used. Additionally, by having it set, it actually makes it hard/impossible for the required changes to land in the other services. Disable/comment out the changes in the Keystone specific lib file for now, and we will re-enable once the Services can make use of them. Change-Id: Ia1de9083c21107dac2f0abb56bda166bdb37a69d --- lib/keystone | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/keystone b/lib/keystone index f9ee8eb761..8db0876f8b 100644 --- a/lib/keystone +++ b/lib/keystone @@ -344,8 +344,8 @@ function configure_keystone { # Configure the project created by the 'keystone-manage bootstrap' as the cloud-admin project. # The users from this project are globally admin as before, but it also # allows policy changes in order to clarify the adminess scope. - iniset $KEYSTONE_CONF resource admin_project_domain_name Default - iniset $KEYSTONE_CONF resource admin_project_name admin + #iniset $KEYSTONE_CONF resource admin_project_domain_name Default + #iniset $KEYSTONE_CONF resource admin_project_name admin } # create_keystone_accounts() - Sets up common required keystone accounts