Andy Ning 5afd5f90b2 update Barbican admin secret's user/project IDs during bootstrap ... In a DC system when subcloud is managed, keystone user/project IDs are synced with Central Cloud, including admin user and project. But the admin's secrets in Barbian still use the original user/project IDs, causing docker registry access failure when platform-integ-apps is reapplied. This change added a patch to keystone puppet manifest, that updates keystone admin user/project IDs to be the same as Central Cloud right after keystone is bootstrapped during subcloud deployment. This way any referece to admin user/project IDs after bootstrap will be using the IDs same as Central Cloud, including the ones in Barbican. This will solve the problem of retrieving central registry credential failure when platform-integ-apps is reapplied. Change-Id: I509a06b4b810620a1b3648837726f7f2771162a5 Closes-Bug: 1851247 Signed-off-by: Andy Ning <andy.ning@windriver.com>		2019-11-08 09:51:24 -05:00
..
facter/centos	Change compute node to worker node personality	2018-12-12 15:09:04 -05:00
puppet-4.8.2/centos	de-fuzz puppet patch	2018-10-09 23:01:46 +08:00
puppet-modules	update Barbican admin secret's user/project IDs during bootstrap	2019-11-08 09:51:24 -05:00