Description of problem: After updating the keystone_domain_specific_ldap_backend.yaml template, a deployment results in incorrect ownership(root:root) of the generated files in /var/lib/config-data/puppet-generated/keystone/etc/keystone/domains. The end user manually had to chown 42425:42425 in order to achieve functionality. Version-Release number of selected component (if applicable): OSP12 How reproducible: Always with LDAP authentication Steps to Reproduce: 1. Configure LDAP authentication 2. Deploy or update Actual results: /var/lib/config-data/puppet-generated/keystone/etc/keystone/domains/blah owned by root:root Expected results: /var/lib/config-data/puppet-generated/keystone/etc/keystone/domains/blah owned by 42425:42425 Additional info:
We got confirmation that after a restart of the container, the file is not owned by 42425 instead of root. Can we integrate the container restart in the update process?
*** This bug has been marked as a duplicate of bug 1537598 ***