Barbican configuration is missing in glance configuration at Edge sites

[Alan Bishop]

The THT for configuring Barbican key manager settings in Glance fail to take into account the tripleo service name is "glance_api_edge" in DCN/Edge deployments (this service name is necessary to avoid deployment conflicts with the glance_api tripleo service deployed in the control plane). As a consequence, when Barbican is part of the deployment, the glance-api.conf files at the Edge sites are missing the settings required to access the barbican-api service in the control plane.

Steps to reproduce:

1. Deploy a control plane overcloud with support for Barbican
2. Deploy an Edge site with the env file [1] that enables cinder, nova and glance to access Barbican in the control plane
3. Examine the service configurations of an Edge node. Barbican key manager settings will be visible in nova.conf and cinder.conf (if cinder is part of the Edge deployment), but they will be missing from glance-api.conf

[1] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/environments/services/barbican-edge.yaml

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 13.1.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 14.0.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 12.4.2 release.

[Alan Bishop (alan-bishop)]

Patch on master (wallaby) [1] has merged.

https://review.opendev.org/c/openstack/tripleo-heat-templates/+/764038

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 11.4.0 release.