[3.9] fact_caching_timeout default value is 86400 or 600 ?
See original GitHub issueDescription
This issue is for checking the specification of openshift-ansible cache timeout default value.
After checking here, I’ll request to modify the documentation related with this issue, if the documentation is not correct.
- The description of documentation: Running the RPM-based Installer
The installer caches playbook configuration values for 10 minutes, by default.
As of v3.10
is configured fact_caching_timeout = 600
in /usr/share/ansible/openshift-ansible/ansible.cfg
, but not v3.9
. As far as I know, in v3.9
ansible refer the /etc/ansible/ansible.cfg
as default, the cache timeout is not specified in ansible.cfg
, so it used as 86400
default timeout value.
https://github.com/ansible/ansible/blob/stable-2.4/lib/ansible/config/base.yml#L272-L280
CACHE_PLUGIN_TIMEOUT:
name: Cache Plugin expiration timeout
default: 86400
description: Expiration timeout for the cache plugin data
env: [{name: ANSIBLE_CACHE_PLUGIN_TIMEOUT}]
ini:
- {key: fact_caching_timeout, section: defaults}
type: integer
yaml: {key: facts.cache.timeout}
Version
- Your ansible version per
ansible --version
ansible 2.4.6.0
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, the docs are correct and RPMs should use 10min timeout, but RPM seems to be copying this file to a different location
I could know the background and cause about this issue, so I’ll close it.