-
Notifications
You must be signed in to change notification settings - Fork 498
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.
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
facter ignored and recalculates facts which should be cached if cache_groups contains spaces like 'desktop management interface' #2712
Comments
The problem is because if facter attempts to resolve a fact like
But that means the cache is effectively disabled if there happens to be one fact in the group that can never be resolved... I think the behavior was introduced in 9b87395#diff-f0f24801215b37a96e44c08052ac98123c0b54de2e18c5a81836811934c438bbR103 to detect if a cached fact is missing after upgrading from puppet 3 to 4. We also don't log anything if we fail to load the cache: facter/lib/facter/framework/core/cache_manager.rb Lines 202 to 203 in 1d46692
|
It seems that before removing in this case it's better to check - probably that string |
|
If one fact is missing in group - we don't want to delete whole facts group - only recalculate missing fact if we need. Should fix puppetlabs#2712
Describe the Bug
facter -d shows that "desktop management interface facts cache file expired, missing or is corrupt" even that it set to cache by settings.
/etc/puppetlabs/facter/facter.conf
Expected Behavior
dmi data should be cached properly and not rerun every run puppet/facter.
Steps to Reproduce
Steps to reproduce the behavior:
facter -d dmi
Environment
Additional Context
files
virtualization
anddesktop management interface
shouldn't changed every puppet run because it should be cached and renewed only one time in 30 days as it set in facter config.Internal tracking ticket https://perforce.atlassian.net/browse/FACT-3209
The text was updated successfully, but these errors were encountered: