Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fact cache being ignored on 2.0? #12213

Closed
mattwillsher opened this issue Sep 2, 2015 · 3 comments
Closed

Fact cache being ignored on 2.0? #12213

mattwillsher opened this issue Sep 2, 2015 · 3 comments
Labels
bug This issue/PR relates to a bug. P2 Priority 2 - Issue Blocks Release
Milestone
2.0

Comments

@mattwillsher
Copy link
Contributor 

ansible 2.0.0 (devel 843138e7d9) last updated 2015/09/02 18:58:01 (GMT +100)
  lib/ansible/modules/core: (detached HEAD ef1f31c652) last updated 2015/08/31 21:19:36 (GMT +100)
  lib/ansible/modules/extras: (detached HEAD 5b39e19387) last updated 2015/08/31 21:19:36 (GMT +100)
  config file = /Users/matt/Development/ansible/ansible.cfg
  configured module search path = None

ansible.cfg

[default]
gathering = smart
fact_caching = jsonfile
fact_caching_connection = factcache
fact_caching_timeout = 86400

In 1.9.2 setup doesn't show up when the cache is used.
2.0.0 calls setup each time and setup appears slower that in 1.9.2/
@jimi-c jimi-c added bug_report P2 Priority 2 - Issue Blocks Release labels Sep 3, 2015
@jimi-c jimi-c added this to the v2 milestone Sep 3, 2015
@jimi-c
Copy link
Member

jimi-c commented Sep 3, 2015

Scratch what I said above, I thought it could be specified at the play level, but was incorrect. Still looking into why it's not picking that setting up.

@jimi-c jimi-c closed this as completed in 4ac2baf Sep 3, 2015
@jimi-c
Copy link
Member

jimi-c commented Sep 3, 2015

Closing This Ticket

Hi!

We believe the above commit should resolve this problem for you. This will also be included in the next major release.

If you continue seeing any problems related to this issue, or if you have any further questions, please let us know by stopping by one of the two mailing lists, as appropriate:

Because this project is very active, we're unlikely to see comments made on closed tickets, but the mailing list is a great way to ask questions, or post if you don't think this particular issue is resolved.

Thank you!

@mattwillsher
Copy link
Contributor Author

That's fixed if for me. Thanks, @jimi-c

@alikins alikins mentioned this issue Sep 28, 2016
Closed
@ansibot ansibot added bug This issue/PR relates to a bug. and removed bug_report labels Mar 6, 2018
@ansible ansible locked and limited conversation to collaborators Apr 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug This issue/PR relates to a bug. P2 Priority 2 - Issue Blocks Release
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
3 participants
@jimi-c @mattwillsher @ansibot