In TripleO we seem to be hitting an issue where get_addr is returning before the output of the referenced resource is ready; this can be seen in the submission at: https://review.openstack.org/#/c/305751
That submission is creating a new output in the endpoint_map.yaml, see [1] and then it's updating the glance-registry role so that it gets its mysql connection string from the new output [2].
The mysql connection string is collected from the endpoint_map output in and passed as parameter to the role in [3]
As a result, the glance connection string ends up being invalid and the puppet module will default to sqlite [4]
In TripleO we seem to be hitting an issue where get_addr is returning before the output of the referenced resource is ready; this can be seen in the submission at: https:/ /review. openstack. org/#/c/ 305751
That submission is creating a new output in the endpoint_map.yaml, see [1] and then it's updating the glance-registry role so that it gets its mysql connection string from the new output [2].
The mysql connection string is collected from the endpoint_map output in and passed as parameter to the role in [3]
As a result, the glance connection string ends up being invalid and the puppet module will default to sqlite [4]
1. https:/ /review. openstack. org/#/c/ 305751/ 8/network/ endpoints/ endpoint_ map.yaml /review. openstack. org/#/c/ 305751/ 8/puppet/ services/ glance- registry. yaml /github. com/openstack/ tripleo- heat-templates/ blob/master/ overcloud. yaml#L878 logs.openstack. org/51/ 305751/ 8/check- tripleo/ gate-tripleo- ci-f22- nonha/ab26e4d/ logs/overcloud- controller- 0.tar.xz
2. https:/
3. https:/
4. http://