Jira (FACT-2878) Networking fact improvements for Aix
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-2878 Networking fact improvements for Aix Change By: Sebastian Miclea Assignee: Sebastian Miclea 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.379328.1606498722000.112642.1610438220029%40Atlassian.JIRA.
Jira (PUP-10847) "puppet facts show fact" output differs from "facter fact"
Title: Message Title Bogdan Irimie updated an issue Puppet / PUP-10847 "puppet facts show fact" output differs from "facter fact" Change By: Bogdan Irimie Sub-team: ghost ghos 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.382201.1609880859000.112637.1610437320045%40Atlassian.JIRA.
Jira (PUP-10847) "puppet facts show fact" output differs from "facter fact"
Title: Message Title Bogdan Irimie updated an issue Puppet / PUP-10847 "puppet facts show fact" output differs from "facter fact" Change By: Bogdan Irimie Sub-team: ghos ghost 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.382201.1609880859000.112638.1610437320100%40Atlassian.JIRA.
Jira (PUP-10823) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu commented on PUP-10823 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 rspec-puppet creates custom facts to overwrite core facts with the data from facterdb: https://github.com/rodjek/rspec-puppet/blob/master/lib/rspec-puppet/support.rb#L479-L483. This works well with facter 2 but facter 4 will still resolve facts, resulting in the observed general slowness. 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.380977.1608048829000.112636.1610437140032%40Atlassian.JIRA.
Jira (FACT-2911) legacy group blocks processors core fact
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2911 legacy group blocks processors core fact Change By: Bogdan Irimie Assignee: Bogdan Irimie 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.382838.161035666.112635.1610436840128%40Atlassian.JIRA.
Jira (FACT-2911) legacy group blocks processors core fact
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2911 legacy group blocks processors core fact Change By: Bogdan Irimie Sprint: ready for triage 2 ghost-13.01.2020 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.382838.161035666.112634.1610436780034%40Atlassian.JIRA.
Jira (PUP-10842) Issue with puppet creating production folder when multiple environment paths are set
Title: Message Title Josh Cooper commented on PUP-10842 Re: Issue with puppet creating production folder when multiple environment paths are set Some background on the "production" directory. When directory environments were introduced in puppet 3.x, "production" was a hardcoded default, and had to exist on the filesystem somewhere, so PUP-2519 and https://github.com/puppetlabs/puppet/commit/8e70dd65a5d5d57b97ca1ae0ff588a232e06bb21#diff-feceffda334b8cc3287b33394350b4ec29a27ae6efad4bbd188e9c892f7107acR1089-R1102 created it. However, puppet could run into problems when running puppet config and other CLI applications that don't need an environment directory. In PUP-6739, we introduced the idea of an environment_mode, so that applications could opt-out, e.g. puppet help, puppet agent, puppet plugin, etc. See also PUP-10796. I think ideally we would never create the "production" directory. but I don't know what assumptions may be built up around that. 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.381531.1608552353000.112606.1610418180131%40Atlassian.JIRA.
Jira (PUP-10845) puppet apply creates warnings (since 7.x)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10845 puppet apply creates warnings (since 7.x) Change By: Josh Cooper Release Notes Summary: Eliminates ruby 2.7.x warnings when running "puppet apply" with node statements 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.381915.1609339994000.112592.1610416560032%40Atlassian.JIRA.
Jira (PUP-10845) puppet apply creates warnings (since 7.x)
Title: Message Title Josh Cooper commented on PUP-10845 Re: puppet apply creates warnings (since 7.x) Passed CI in fdeab5be29364dd7210327ef901eb7d39f7cde35 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.381915.1609339994000.112591.1610416500021%40Atlassian.JIRA.
Jira (PUP-10818) Cached catalog contains the result of deferred evaluation instead of the deferred function
Title: Message Title Josh Cooper commented on PUP-10818 Re: Cached catalog contains the result of deferred evaluation instead of the deferred function There's a problem with this change, as we are no longer performing type/provider validation of the catalog before caching it. 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.380551.1607542151000.112590.1610415780033%40Atlassian.JIRA.
Jira (PUP-10818) Cached catalog contains the result of deferred evaluation instead of the deferred function
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10818 Cached catalog contains the result of deferred evaluation instead of the deferred function Change By: Josh Cooper Sprint: Platform Core KANBAN 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.380551.1607542151000.112589.1610415420025%40Atlassian.JIRA.
Jira (PDB-4524) Provide way to stop/start command processing (maybe only internal initially)
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4524 Provide way to stop/start command processing (maybe only internal initially) Change By: Zachary Kent Labels: tsr-pdb-backlog 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.327600.1569963418000.112584.1610414460079%40Atlassian.JIRA.
Jira (PDB-4934) PuppetDB does not support username@hostname auth for Azure PostgreSQL
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4934 PuppetDB does not support username@hostname auth for Azure PostgreSQL Change By: Zachary Kent Labels: tsr-pdb-backlog 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.375238.1603127441000.112583.1610414460036%40Atlassian.JIRA.
Jira (PDB-2488) Don't accept trailing garbage in query string
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-2488 Don't accept trailing garbage in query string Change By: Zachary Kent Labels: tsr-pdb-backlog 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.119258.145685283.112581.1610414400171%40Atlassian.JIRA.
Jira (PDB-4172) Allow metrics during startup
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4172 Allow metrics during startup Change By: Zachary Kent Labels: tsr-pdb-backlog 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.282135.1540387252000.112582.1610414400215%40Atlassian.JIRA.
Jira (PDB-3418) Add a new-fact-time metric to complement the new-catalog-time metric
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3418 Add a new-fact-time metric to complement the new-catalog-time metric Change By: Zachary Kent Labels: tsr-pdb-backlog 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.184154.1491345864000.112580.1610414400124%40Atlassian.JIRA.
Jira (PDB-3159) I'd like to access the performance dashboard over https
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3159 I'd like to access the performance dashboard over https Change By: Zachary Kent Labels: tcse tsr-pdb-backlog 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.159265.1478038793000.112579.1610414400068%40Atlassian.JIRA.
Jira (PUP-10819) Improve error handling when a 3x function is deferred
Title: Message Title
Josh Cooper commented on PUP-10819
Re: Improve error handling when a 3x function is deferred
I went down the rabbit hole to understand what the issue was. And I think there's a pretty trivial fix for this. When resolving deferred values, puppet creates a DeferredResolver which creates a script compiler and scope: https://github.com/puppetlabs/puppet/blob/fdeab5be29364dd7210327ef901eb7d39f7cde35/lib/puppet/pops/evaluator/deferred_resolver.rb#L22. When running puppet apply, the catalog.environment_instance and Puppet.lookup(:current_environment) are the same object. The compiler ends up creating an anonymous module based on the catalog.environment_instance and defining instance methods on that module. https://github.com/puppetlabs/puppet/blob/fdeab5be29364dd7210327ef901eb7d39f7cde35/lib/puppet/parser/functions.rb#L205-L222 The compiler's scope object then extends the environment module, so that the environment module's methods are instance methods on the scope, e.g. Scope#function_sprintf. https://github.com/puppetlabs/puppet/blob/fdeab5be29364dd7210327ef901eb7d39f7cde35/lib/puppet/parser/scope.rb#L1124 The problem is that Puppet::Parser::Functions.environment_module(environment) only memoizes the module if the environment object is exactly the same. It doesn't memoize if a different environment object with the same name:
irb(main):014:0> env = Puppet::Node::Environment.remote('env1')
=>
irb(main):015:0> Puppet::Parser::Functions.environment_module(env)
=> #
irb(main):016:0> Puppet::Parser::Functions.environment_module(env)
=> #
irb(main):017:0> Puppet::Parser::Functions.environment_module(Puppet::Node::Environment.remote('env1'))
=> #
Jira (PDB-2476) null? operator doesn't work on resource params
Title: Message Title Austin Blatt commented on PDB-2476 Re: null? operator doesn't work on resource params This is the same error as was fixed in PDB-3902. 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.118646.1456440296000.112500.1610408820031%40Atlassian.JIRA.
Jira (PUP-10850) Puppet facts show doesn't have an opt out option for legacy facts
Title: Message Title Oana Tanasoiu updated an issue Puppet / PUP-10850 Puppet facts show doesn't have an opt out option for legacy facts Change By: Oana Tanasoiu Sprint: ghost-13.01.2020 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.382858.1610379246000.111732.1610379300155%40Atlassian.JIRA.
Jira (PUP-10850) Puppet facts show doesn't have an opt out option for legacy facts
Title: Message Title Oana Tanasoiu created an issue Puppet / PUP-10850 Puppet facts show doesn't have an opt out option for legacy facts Issue Type: Bug Assignee: Oana Tanasoiu Created: 2021/01/11 7:34 AM Priority: Normal Reporter: Oana Tanasoiu Puppet Version: 7.0.1 Puppet Server Version: - OS Name/Version: All By default puppet facts show displays legacy facts, there is an option (--show-legacy) that has no effect. There isn't any way to indicate puppet to not retrieve legacy facts. Desired Behavior: Add option --no-legacy to disable legacy facts. Add Comment
Jira (FACT-2912) Fix Jenkins please test this
Title: Message Title Andrei Filipovici created an issue Facter / FACT-2912 Fix Jenkins please test this Issue Type: Task Assignee: Unassigned Created: 2021/01/11 7:05 AM Priority: Normal Reporter: Andrei Filipovici Because the master branch got renamed to 6.x, when running acceptance tests with Jenkins we get an error that the master branch is missing. Some modifications in the CI-job-config project are required. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-10844 Agent failures with server_list when one puppetserver fails Change By: Dorin Pleava Assignee: Dorin Pleava 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.381638.1608653215000.111680.1610376300184%40Atlassian.JIRA.
Jira (PUP-10823) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu commented on PUP-10823 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 I would expect the test to use the facts from facterdb trough the rspec-puppet/rspec-puppet-facts/facterdb combination. 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.380977.1608048829000.111681.1610376300233%40Atlassian.JIRA.
Jira (PUP-10823) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title
Gheorghe Popescu commented on PUP-10823
Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Running a dummy test(` it { is_expected.to compile.with_all_deps } `) seems that 41% of the runtime is lost in Facter 4 `block (2 levels) in execute_command - /usr/local/rvm/gems/ruby-2.6.6/gems/facter-4.0.47/lib/facter/custom_facts/core/execution/base.rb:77 ` Added a puts in the Facter.execute:
puppet_agent
when PE on RedHat
command: /usr/bin/apt-get -s -o Debug::NoLocking=true upgrade 2>&1
0.8899572720001743
command: /usr/bin/apt-get -s -o Debug::NoLocking=true dist-upgrade 2>&1
1.113952480647
command: ip link show
0.00398667767573
command: ip link show lo
0.003320058993796
command: dhcpcd -U lo
0.0021536759995797183
Jira (PUP-7559) puppet doesn't specify file type to get default selinux context
Title: Message Title Alfredo Moralejo updated an issue Puppet / PUP-7559 puppet doesn't specify file type to get default selinux context Change By: Alfredo Moralejo Priority: High Major 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.191580.1495040547000.111630.1610374800043%40Atlassian.JIRA.
Jira (PUP-10823) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu commented on PUP-10823 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 This is also affecting puppet-agent module(and many other i guess) https://github.com/puppetlabs/puppetlabs-puppet_agent/runs/1679329961?check_suite_focus=true Tracked the slowness to an update of facterdb(1.5.0) which loosen dependency on facter from <4 to <5, allowing the install of facter 4 when running unit test. 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.380977.1608048829000.111624.1610373060030%40Atlassian.JIRA.
Jira (FACT-2876) Networking fact improvements for Windows
Title: Message Title Oana Tanasoiu commented on FACT-2876 Re: Networking fact improvements for Windows Facter 3 and facter 4 output are identical, the test scenario implied deactivating an interface. 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.379326.1606498561000.111596.1610365740029%40Atlassian.JIRA.
Jira (PDB-4999) Improve PQL docs by adding entities and parameters
Title: Message Title Claire Cadman moved an issue PuppetDB / PDB-4999 Improve PQL docs by adding entities and parameters Change By: Claire Cadman Key: DOC PDB - 3956 4999 Workflow: Documentation Scrum Team Workflow Project: Documentation [Internal] PuppetDB 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.298419.1551813508000.111526.1610359380080%40Atlassian.JIRA.
Jira (FACT-2911) legacy group blocks processors core fact
Title: Message Title
Bogdan Irimie created an issue
Facter / FACT-2911
legacy group blocks processors core fact
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/01/11 1:17 AM
Priority:
Normal
Reporter:
Bogdan Irimie
When blocking the `legacy` group, `processors` core facts is blocked as well. facter.conf
facts : {
blocklist : [ "legacy" ],
}
Add Comment
Jira (FACT-2882) Facter 4.0.x on Windows does not return the domain when set in the registry
Title: Message Title Oana Tanasoiu commented on FACT-2882 Re: Facter 4.0.x on Windows does not return the domain when set in the registry Sanjay Tripathi thank you for confirming the fix. A new release should be available on 20th this month. 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.379598.1606874598000.111484.1610356500094%40Atlassian.JIRA.
