Jira (PUP-8048) puppet / facter fails randomly in low memory situations
Title: Message Title Josh Cooper commented on PUP-8048 Re: puppet / facter fails randomly in low memory situations The Debian packages of puppet install facter 2.4.6 (the ruby version). It is entirely possible that the old ruby facter implementation required more/excessive amount of memory due to the way it executed the same facts multiple times. We don’t have the engineering resources to investigate this issue, so I'm going to close it. Feel free to reopen if you see the same issue with the puppet-agent packages provided by Puppet. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.216102.1507905599000.123756.1569964080341%40Atlassian.JIRA.
Jira (PUP-8048) puppet / facter fails randomly in low memory situations
Title: Message Title Florian Klink commented on PUP-8048 Re: puppet / facter fails randomly in low memory situations Running facter --debug alone doesn't fail, and shows a value for operatingsystem. Doing the initial puppet run fails reproducible on a VM with 128MB RAM. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8048) puppet / facter fails randomly in low memory situations
Title: Message Title Eric Sorenson commented on PUP-8048 Re: puppet / facter fails randomly in low memory situations Florian - this will be a bit hard to reproduce, and you're right that it's not really "supported" to run puppet in 128mb RAM. Ruby is probably going to fail in bizarre ways that Puppet does not have visibility into. Can you confirm that running facter --debug by itself fails on this system? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8048) puppet / facter fails randomly in low memory situations
Title: Message Title Eric Sorenson assigned an issue to Florian Klink Puppet / PUP-8048 puppet / facter fails randomly in low memory situations Change By: Eric Sorenson Assignee: Florian Klink Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8048) puppet / facter fails randomly in low memory situations
Title: Message Title
Florian Klink created an issue
Puppet / PUP-8048
puppet / facter fails randomly in low memory situations
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/10/13 7:39 AM
Priority:
Normal
Reporter:
Florian Klink
I accidentially created a VM with only 128MB RAM. Puppet run looks like this:
{{Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Error: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Error: Could not autoload puppet/provider/service/openbsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Error: Could not retrieve local facts: Could not autoload puppet/provider/service/openbsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Error: Failed to apply catalog: Could not retrieve local facts: Could not autoload puppet/provider/service/openbsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass}}
This is due to Facter.value(:operatingsystem) being NilClass. When running with --debug, I see a lot of the following messages:Debug: Facter: value for is still nil
It took me a while to find out the puppet run succeeds with more memory just fine. I didn't see any OOM-Killings in dmesg. Of course, it might be not supported/advised to run puppet on such low memory, but I'd still expect puppet to somehow fail in a better way… This might boil down to facter failing in weird ways, puppet not noticing that, or something in between.
puppet-4.8.2-5 on Debian Stretch with packages provided by Debian directly.
