tripleo-heat-templates/common
Alex Schultz 44636dde61 Improve facter cache reliability
We don't need to be caching EC2 metadata in our facter runs because we
don't use this. By leaving this on, it can cause problems when run on
VMs in a cloud that might support EC2.  By having this enabled, we can
see deployments failing to configure nodes because it timesout:

2020-05-13 22:38:30.574339 ERROR puppetlabs.facter - EC2 user data
request failed: Timeout was reached

Additionally if facter fails to generate the cache, the subsequent
puppet runs will fail. This change also added retries to the facter
cache call to ensure that we should be able to generate the cache if an
external fact call fails for some reason.

NOTE: The master patch for this is against tripleo-ansible

Closes-Bug: #1861917
Change-Id: Iaaed0dcf747ca4a08f8e200b43d0f2259ad0ed39
(cherry-picked from c3b57d6a6c26acf35168fea7303fc485e1dcd13f)
2020-06-03 14:14:06 +00:00
..
services Make krb-service-principal metadata per-Role 2019-05-29 10:42:19 +02:00
deploy-steps-tasks.yaml Improve facter cache reliability 2020-06-03 14:14:06 +00:00
deploy-steps.j2 deploy-steps: use lookup() to get pre|post_deployments_role variables 2019-12-14 10:34:47 -05:00
post.j2.yaml Consolidate puppet/docker deployments with one deploy steps workflow 2017-08-11 17:25:02 +00:00