Jira (PUP-10774) Long query time for AD groups
Title: Message Title Reid Vandewiele commented on PUP-10774 Re: Long query time for AD groups Question: on the FFI github page, there is this warning: On Linux systems running with PaX (Gentoo, Alpine, etc.), FFI may trigger mprotect errors. You may need to disable mprotect for ruby (paxctl -m [/path/to/ruby]) for the time being until a solution is found. Would we need to worry about this at all on our supported platforms, if we start using FFI, LIBC, and getgrouplist? I don't know how PaX/mprotect works but it seems like even if a customer did have it installed we might be okay since we're only linking LIBC, and I'm sure that's already being used by Ruby. Figured it was worth asking the question though. 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.377144.160449921.74227.1604706300203%40Atlassian.JIRA.
Jira (PDB-4945) Allow configuring the fact cache type to be json
Title: Message Title Josh Cooper commented on PDB-4945 Re: Allow configuring the fact cache type to be json This was released in puppetlabs-puppetdb in 7.7.0 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.376183.1603814027000.74119.1604696940084%40Atlassian.JIRA.
Jira (PDB-4945) Allow configuring the fact cache type to be json
Title: Message Title Josh Cooper updated an issue PuppetDB / PDB-4945 Allow configuring the fact cache type to be json Change By: Josh Cooper Should this be The puppetdb module will configure the new default? fact cache to json when puppetserver is version 7 or above. When running on earlier versions of puppetserver or when running puppet apply, it will continue to use yaml. 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.376183.1603814027000.74118.1604696940039%40Atlassian.JIRA.
Jira (PUP-10775) Puppet agent fails with `Failed to deserialize Puppet::Resource::Catalog`
Title: Message Title Henrik Lindberg commented on PUP-10775 Re: Puppet agent fails with `Failed to deserialize Puppet::Resource::Catalog` A guess here is that binary files that cause it to fail contain sequences that result in invalid UTF-8 encoding. There is a function binary_file() that works like the file() function but it returns a Binary data type instead of a String. That function should be used instead of file() for binary content. This is supported since puppet 6 where the "rich data" catalog format is the default format (it can serialize all of the data types in the Puppet type system in two different encodings; JSON or Msgpack, where JSON is the default). In addition to handling instance of the Binary data type, it also does the right thing if it gets a string in ASCII-8bit encoding as it will be treated the same way as Binary. In a JSON encoding the binary content will be Base64 encoded text, and in Msgpack it will be a Msgpack binary. Hope that helps. 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.377304.1604596654000.73826.1604671620027%40Atlassian.JIRA.
Jira (PUP-10775) Puppet agent fails with `Failed to deserialize Puppet::Resource::Catalog`
Title: Message Title
Tim Meusel commented on PUP-10775
Re: Puppet agent fails with `Failed to deserialize Puppet::Resource::Catalog`
wopwop, some progress \o/ I created a testenv and checked it for all binary files:
...
root@puppetserver ~ # shopt -s globstar
root@puppetserver ~ # file /etc/puppetlabs/code/environments/msgpack2/modules/*/files/**/* | grep ELF
/etc/puppetlabs/code/environments/msgpack2/modules/mcollective_agent_dockerinfo/files/mcollective/agent/dockerinfo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), not stripped
/etc/puppetlabs/code/environments/msgpack2/modules/mcollective_agent_user/files/mcollective/agent/user: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped
...
root@puppetserver ~ #
There were some more binary blobs. All not listed blobs are distributed like this:
file {'bla':
ensure => file,
source => '///..'
Jira (FACT-2274) Implement debugging API
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2274 Implement debugging API Change By: Bogdan Irimie Fix Version/s: FACT 4.0.45 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.341780.1578907539000.73796.1604657040141%40Atlassian.JIRA.
Jira (FACT-1957) Create class hierarchy that accommodates nested facts
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1957 Create class hierarchy that accommodates nested facts Change By: Bogdan Irimie Fix Version/s: FACT 4.0.45 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.317049.1563427805000.73795.1604656920029%40Atlassian.JIRA.
Jira (FACT-2854) Empty string in blocklist blocks all core facts
Title: Message Title Florin Dragos assigned an issue to Florin Dragos Facter / FACT-2854 Empty string in blocklist blocks all core facts Change By: Florin Dragos Assignee: Florin Dragos 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.377407.1604652706000.73784.1604654580031%40Atlassian.JIRA.
Jira (FACT-2854) Empty string in blocklist blocks all core facts
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2854 Empty string in blocklist blocks all core facts Change By: Bogdan Irimie Sprint: ready for triage ghost-11.11 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.377407.1604652706000.73783.1604652720107%40Atlassian.JIRA.
Jira (FACT-2854) Empty string in blocklist blocks all core facts
Title: Message Title
Bogdan Irimie created an issue
Facter / FACT-2854
Empty string in blocklist blocks all core facts
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/11/06 12:51 AM
Priority:
Blocker
Reporter:
Bogdan Irimie
If we configure the blocklist form facter.conf with an empty string all facts are blocked. e.g.
facts : {
blocklist : [ "" ],
...
}
Jira (FACT-2853) Command from help message should contain - instead of _
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2853 Command from help message should contain - instead of _ Change By: Bogdan Irimie Sprint: ready for triage ghost-11.11 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.377406.1604649704000.73776.1604650320026%40Atlassian.JIRA.
Jira (FACT-2853) Command from help message should contain - instead of _
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2853 Command from help message should contain - instead of _ Change By: Bogdan Irimie Priority: Normal Blocker 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.377406.1604649704000.73775.1604650260025%40Atlassian.JIRA.
Jira (FACT-2853) Command from help message should contain - instead of _
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2853 Command from help message should contain - instead of _ Issue Type: Task Assignee: Unassigned Created: 2020/11/06 12:01 AM Priority: Normal Reporter: Bogdan Irimie Help output with `_` instead of `-` [--color] Enable color output. [--no_color] Disable color output. -c [--config] The location of the config file. [--custom_dir] A directory to use for custom facts. -d [--debug] Enable debug output. [--external_dir] A directory to use for external facts.
