Trove service user configuration should be aligned
In the case of trove, we follow service configuration as per the official manual installation documentation [1]. It uses trove_for_trove_usage as a service tenant unlike other openstack services which uses default service tenant. For any project service to work, the configuration [keystone_authtoken] section should be updated with the correct user, project, tenant and password. Proposed change fixes this issue so Trove service configurations are aligned with the trove admin user settings for tenant and password. [1]: http://docs.openstack.org/developer/trove/dev/manual_install.html Closes-bug: #1644079 Change-Id: I92a426132e20669731bc65526b20f60a3f34b348
This commit is contained in:
chhagarw
committed by
Jean-Philippe Evrard
parent
b9babfe3f4
commit
eefe3d66c1
2 changed files with 3 additions and 3 deletions
@@ -36,11 +36,11 @@ trove_regular_user_name: regular_trove_user
trove_admin_user_name:admin_trove_user
trove_service_name:trove
trove_service_user_name:trove
trove_service_user_name:"{{ trove_admin_user_name }}"
trove_service_tenant_name:trove_for_trove_usage
trove_service_type:database
trove_service_description:"OpenStack DBaaS (Trove)"
trove_service_project_name:service
trove_service_project_name:"{{ trove_service_tenant_name }}"
trove_service_admin_role_names:
- admin
trove_service_region:RegionOne
@@ -88,7 +88,7 @@
insecure:"{{ keystone_service_adminuri_insecure }}"
user_name:"{{ trove_admin_user_name }}"
tenant_name:"{{ trove_service_tenant_name }}"
password:"{{ trove_admin_user_password }}"
password:"{{ trove_service_password }}"
project_name:"{{ trove_service_project_name }}"
register:add_trove_admin_user
until:add_trove_admin_user |success
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.