Description of problem: After packstack installation I see that some components have authtoken middleware parameters set in paste.ini instead of application's main .conf e.g. BAD /etc/cinder/cinder.conf:admin_tenant_name = %SERVICE_TENANT_NAME% /etc/cinder/cinder.conf:admin_user = %SERVICE_USER% /etc/cinder/cinder.conf:admin_password = %SERVICE_PASSWORD% /etc/cinder/api-paste.ini:admin_password=cinder_default_password /etc/cinder/api-paste.ini:admin_tenant_name=services /etc/cinder/api-paste.ini:admin_user=cinder /etc/nova/api-paste.ini:admin_user=nova /etc/nova/api-paste.ini:admin_password=nova_default_password /etc/nova/api-paste.ini:admin_tenant_name=services vs GOOD /etc/glance/glance-api.conf:admin_tenant_name = services /etc/glance/glance-api.conf:admin_user = glance /etc/glance/glance-api.conf:admin_password = glance_default_password /etc/glance/glance-registry.conf:admin_tenant_name = services /etc/glance/glance-registry.conf:admin_user = glance /etc/glance/glance-registry.conf:admin_password = glance_default_password Version-Release number of selected component (if applicable): openstack-packstack-2012.2.2-0.1.dev205.el6ost Related docs bug 876763
Also related bug 887334 dumping puppet templates over distributed config files removes that effort ideally augeas or something could be used to edit them instead?
Fix for the nova part of this submitted upstream https://review.openstack.org/21995
Fix for the cinder part of this submitted upstream https://review.openstack.org/21997
Verified NVR: openstack-packstack-2012.2.3-0.1.dev454.el6ost.noarch Installed Openstack using packstack. /etc/cinder/cinder.conf ======================= admin_tenant_name = services admin_user = cinder admin_password = 46b82b2e07984345 /etc/cinder/api-paste.ini ========================= admin_password, admin_tenant_name and admin_user are no longer present in this file. /etc/nova/api-paste.ini ======================= admin_user, admin_password and admin_tenant_name are no longer present in this file.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0671.html