Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Oana Tanasoiu commented on FACT-2924 Re: Facter fails "closed" if the facter.conf file is invalid I've created created a new ticket for the reported problem: https://tickets.puppetlabs.com/browse/FACT-2960 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383703.1611082995000.161927.1615369740035%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Mihai Buzgau commented on FACT-2924 Re: Facter fails "closed" if the facter.conf file is invalid These changes were already released, we need a new ticket for this. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383703.1611082995000.161911.1615367280027%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Oana Tanasoiu commented on FACT-2924 Re: Facter fails "closed" if the facter.conf file is invalid Hi Tom Parker , Good catch! The failure you're seeing is because we didn't accept forms like 'day', only 'days' and it's not because of the JSON form (which is hocon validated). A pull request was opened to fix this issue. Thank you for reporting this! Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383703.1611082995000.161885.1615365480143%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Tom Parker updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Tom Parker Attachment: facter.conf Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383703.1611082995000.160985.1615311240032%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title
Tom Parker commented on FACT-2924
Re: Facter fails "closed" if the facter.conf file is invalid
This is still not 100% fixed. On puppet-agent.x86_64 0:7.4.1-1.el7 I can't even run a puppet agent --version without a crash. My badly formatted facter.conf (caused by erroneously converting to json unstead of hocon) is: {{{ }} {{ "facts": { }} {{ "blocklist": null, }} {{ "ttls": [ }} {{ { }} {{ "EC2": "1 day" }} {{ } }} {{ ] }} {{ } }} } [LIVE] gredb1 [k: gredb]:~ # puppet agent --version Traceback (most recent call last): 21: from /opt/puppetlabs/puppet/bin/puppet:4:in `' 20: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' 19: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' 18: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `' 17: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' 16: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' 15: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:15:in `' 14: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' 13: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' 12: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:10:in `' 11: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:13:in `' 10: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options.rb:40:in `init' 9: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options/config_file_options.rb:12:in `init' 8: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options/config_file_options.rb:24:in `augment_all' 7: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options/config_file_options.rb:93:in `augment_facts' 6: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options/config_file_options.rb:93:in `new' 5: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:16:in `initialize' 4: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:83:in `load_facts_ttls' 3: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:83:in `each' 2: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:84:in `block in load_facts_ttls' 1: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:106:in `ttls_to_seconds' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:106:in `*': nil can't be coerced into Integer (TypeError)
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Claire Cadman updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Claire Cadman Labels: doc_reviewed docs-reviewed Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383703.1611082995000.134146.1612517400147%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Claire Cadman updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Claire Cadman Labels: doc_reviewed docs-reviewed Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383703.1611082995000.134145.1612517400099%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Claire Cadman updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Claire Cadman Labels: doc_reviewed Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383703.1611082995000.134137.1612516980039%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Ciprian Badescu Fix Version/s: FACT 4.0.50 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383703.1611082995000.133021.1612435140098%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Oana Tanasoiu Release Notes: Bug Fix Release Notes Summary: Description of the problem: Facter fails when an invalid config file is provided.Description of the fix: Log a warning message stating that the parsing of config file failed and continue retrieving facts with the default options. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383703.1611082995000.125803.1611737220138%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383703.1611082995000.119305.1611146880040%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Mihai Buzgau Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383703.1611082995000.119216.1611136860083%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Mihai Buzgau Sprint: NW - 2021-02-03 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383703.1611082995000.119215.1611136860040%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.383703.1611082995000.119214.1611136800134%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Tom Parker updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Tom Parker With facter 4 shipped with puppet 7.1 is if the facter.conf file is invalid facter fails to load at all which prevents all subsequent puppet runs. This means that instead of being able to fix the problem with a puppet run the administrator has to login to any affected server and fix the file by hand. Would it be possible to fail "open" if the file is invalid? Log an error and run with all defaults? This would at least allow puppet to fix the problem on a subsequent run. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Tom Parker created an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Issue Type: Bug Assignee: Unassigned Created: 2021/01/19 11:03 AM Priority: Normal Reporter: Tom Parker With facter 4 shipped with puppet 7.1 is the facter.conf file is invalid facter fails to load at all which prevents all subsequent puppet runs. This means that instead of being able to fix the problem with a puppet run the administrator has to login to any affected server and fix the file by hand. Would it be possible to fail "open" if the file is invalid? Log an error and run with all defaults? This would at least allow puppet to fix the problem on a subsequent run. Add Comment
