Jira (FACT-3116) facter fails when using cached facts in a read-only filesystem

[Josh Cooper (Jira)]

Title: Message Title

Josh Cooper updated an issue   Facter / FACT-3116 facter fails when using cached facts in a read-only filesystem Change By: Josh Cooper When using cached facts in a read-only filesystem, facter fails with error: {noformat} [root@a41691fe3b11 ~]# facter --config facter.conf --debug [2022-04-26 16:00:36.720327 ] INFO Facter - executed with command line: --config facter.conf --debug [2022-04-26 16:00:36.720370 ] DEBUG Facter - Facter version: 4.2.8 [2022-04-26 16:00:36.720386 ] DEBUG Facter - blocking collection of EC2 facts [2022-04-26 16:00:36.720436 ] DEBUG Facter::ClassDiscoverer - There is no module named Centos [2022-04-26 16:00:36.722209 ] DEBUG Facter::FactManager - Resolving facts sequentially [2022-04-26 16:00:36.723969 ] DEBUG Facter::FactLoader - Loading all internal facts [2022-04-26 16:00:36.728158 ] DEBUG Facter::FactLoader - Loading custom facts [2022-04-26 16:00:36.729015 ] DEBUG Facter::FactLoader - Loading external facts /usr/share/gems/gems/facter-4.2.8/lib/facter/framework/core/cache_manager.rb:229:in `delete': Read-only file system @ apply2files - /opt/puppetlabs/facter/cache/cached_facts/operating system (Errno::EROFS)         from /usr/share/gems/gems/facter-4.2.8/lib/facter/framework/core/cache_manager.rb:229:in `delete_cache'         from /usr/share/gems/gems/facter-4.2.8/lib/facter/framework/core/cache_manager.rb:99:in `read_fact'         from /usr/share/gems/gems/facter-4.2.8/lib/facter/framework/core/cache_manager.rb:76:in `resolve_fact'         from /usr/share/gems/gems/facter-4.2.8/lib/facter/framework/core/cache_manager.rb:17:in `block in resolve_facts'         from /usr/share/gems/gems/facter-4.2.8/lib/facter/framework/core/cache_manager.rb:16:in `delete_if'         from /usr/share/gems/gems/facter-4.2.8/lib/facter/framework/core/cache_manager.rb:16:in `resolve_facts'         from /usr/share/gems/gems/facter-4.2.8/lib/facter/framework/core/fact_manager.rb:22:in `resolve_facts'         from /usr/share/gems/gems/facter-4.2.8/lib/facter.rb:521:in `resolve_facts_for_user_query'         from /usr/share/gems/gems/facter-4.2.8/lib/facter.rb:454:in `to_user_output'         from /usr/share/gems/gems/facter-4.2.8/lib/facter/framework/cli/cli.rb:124:in `query'         from /usr/share/gems/gems/thor-1.1.0/lib/thor/command.rb:27:in `run'         from /usr/share/gems/gems/thor-1.1.0/lib/thor/invocation.rb:127:in `invoke_command'         from /usr/share/gems/gems/thor-1.1.0/lib/thor.rb:392:in `dispatch'         from /usr/share/gems/gems/thor-1.1.0/lib/thor/base.rb:485:in `start'         from /usr/share/gems/gems/facter-4.2.8/lib/facter/framework/cli/cli_launcher.rb:23:in `start'         from /usr/bin/facter:10:in `<main>' {noformat} I'm running this in a centos8 container and my facter.conf file is: {code:hocon} facts : {     blocklist: [ "EC2" ],     cache: true     ttls: [       { "kernel" : 8 hour },       { "memory" : 8 hour },       { "networking" : 8 hour },       { "operating system" : 8 hour },       { "processor" : 8 hour },     ]   }    {code} Note this worked fine with facter 3.14. Add Comment   This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.444812.1650992200000.21414.1651256580044%40Atlassian.JIRA.