Jira (PUP-10417) Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10417 Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet Change By: Jarret Lavallee CS Priority: Needs Priority 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.354928.1586391583000.34492.1586392620026%40Atlassian.JIRA.
Jira (PUP-10417) Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet
Title: Message Title
Garrett Guillotte updated an issue
Puppet / PUP-10417
Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet
Change By:
Garrett Guillotte
*Puppet Version:* Seen in Puppet 5 and 6*Puppet Server Version:* N/A*OS Name/Version:* RHEL 7If a custom function defines a Ruby module also used by Puppet (ie. {{module JSON}}), and other loaded modules attempt to use related functions (ie. JSON functions from {{stdlib}} that call {{JSON}}), they fail because Puppet runs the custom function code within the {{Puppet::Pops::Loader::RubyFunctionInstantiator}} scope instead of top scope:{code}2020-03-18T00:00:29.762-05:00 ERROR [qtp802169583-480691] [puppetserver] Puppet Evaluation Error: Error while evaluating a Function Call, undefined method `pretty_generate' for Puppet::Pops::Loader::RubyFunctionInstantiator::JSON:Module (file: /etc/puppetlabs/code/environments/production/modules/npc_coreservices/manifests/components/cache_proxy/install.pp, line: 106, column: 22) on node pv20616cspgl01.npc.lan/etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/to_json_pretty.rb:36:in `to_json_pretty'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/dispatch.rb:60:in `invoke'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/dispatcher.rb:43:in `block in dispatch'org/jruby/RubyKernel.java:1180:in `catch'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/dispatcher.rb:42:in `dispatch'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/function.rb:46:in `block in call'org/jruby/RubyKernel.java:1180:in `catch'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/function.rb:45:in `call'/etc/puppetlabs/code/environments/production/modules/.../manifests/components/cache_proxy/install.pp:106:in `'org/jruby/RubyKernel.java:1037:in `eval'...{code}For example, a Puppet module with a custom Ruby function that declares:{code}require 'json'module JSON...{code}and another Puppet module that attempts to prettify JSON via {{stdlib}}:{code}$json = to_json_pretty($some_json_content){code}can produce the above error.For another example, see:https://github.com/sensu/puppet-module-sensuclassic/issues/24and the patch to work around it:https://github.com/sensu/puppet-module-sensuclassic/pull/25/files*Desired Behavior:*Users can define a Ruby JSON module in a custom function if necessary without breaking default behavior.*Actual Behavior:*{{stdlib}} doesn't explicitly defines the correct scope when invoking {{JSON}} (MODULES ticket tbd -10623 ), so an {{eval()}} statement in {{RubyFunctionInstantiator}} executes the code within its scope instead.https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/loader/ruby_function_instantiator.rb#L22If custom Ruby functions cannot be guaranteed to run in the expected scope, or if module declarations are unsafe, this behavior should at a minimum be documented, and if possible the error messages should indicate the scope conflict.
Jira (PUP-10417) Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet
Title: Message Title Garrett Guillotte updated an issue Puppet / PUP-10417 Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet Change By: Garrett Guillotte 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.354928.1586391583000.34485.1586391720037%40Atlassian.JIRA.
Jira (PUP-10417) Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet
Title: Message Title
Garrett Guillotte updated an issue
Puppet / PUP-10417
Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet
Change By:
Garrett Guillotte
*Puppet Version:* Seen in Puppet 5 and 6*Puppet Server Version:* N/A*OS Name/Version:* RHEL 7If a custom function defines a Ruby module also used by Puppet (ie. {{module JSON}}), and other loaded modules attempt to use related functions (ie. JSON functions from {{stdlib}} that call {{JSON}}), they fail because Puppet runs the custom function code within the {{Puppet::Pops::Loader::RubyFunctionInstantiator}} scope instead of top scope:{code}2020-03-18T00:00:29.762-05:00 ERROR [qtp802169583-480691] [puppetserver] Puppet Evaluation Error: Error while evaluating a Function Call, undefined method `pretty_generate' for Puppet::Pops::Loader::RubyFunctionInstantiator::JSON:Module (file: /etc/puppetlabs/code/environments/production/modules/npc_coreservices/manifests/components/cache_proxy/install.pp, line: 106, column: 22) on node pv20616cspgl01.npc.lan/etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/to_json_pretty.rb:36:in `to_json_pretty'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/dispatch.rb:60:in `invoke'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/dispatcher.rb:43:in `block in dispatch'org/jruby/RubyKernel.java:1180:in `catch'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/dispatcher.rb:42:in `dispatch'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/function.rb:46:in `block in call'org/jruby/RubyKernel.java:1180:in `catch'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/function.rb:45:in `call'/etc/puppetlabs/code/environments/production/modules/ npc_coreservices ... /manifests/components/cache_proxy/install.pp:106:in `'org/jruby/RubyKernel.java:1037:in `eval'...{code}For example, a Puppet module with a custom Ruby function that declares:{code}require 'json'module JSON...{code}and another Puppet module that attempts to prettify JSON via {{stdlib}}:{code}$json = to_json_pretty($some_json_content){code}can produce the above error.For another example, see:https://github.com/sensu/puppet-module-sensuclassic/issues/24and the patch to work around it:https://github.com/sensu/puppet-module-sensuclassic/pull/25/files*Desired Behavior:*Users can define a Ruby JSON module in a custom function if necessary without breaking default behavior.*Actual Behavior:*{{stdlib}} doesn't explicitly defines the correct scope when invoking {{JSON}} (MODULES ticket tbd), so an {{eval()}} statement in {{RubyFunctionInstantiator}} executes the code within its scope instead.https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/loader/ruby_function_instantiator.rb#L22If custom Ruby functions cannot be guaranteed to run in the expected scope, or if module declarations are unsafe, this behavior should at a minimum be documented, and if possible the error messages should indicate the scope
Jira (PUP-10417) Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet
Title: Message Title Garrett Guillotte created an issue Puppet / PUP-10417 Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet Issue Type: Bug Assignee: Unassigned Created: 2020/04/08 5:19 PM Priority: Normal Reporter: Garrett Guillotte Puppet Version: Seen in Puppet 5 and 6 Puppet Server Version: N/A OS Name/Version: RHEL 7 If a custom function defines a Ruby module also used by Puppet (ie. module JSON), and other loaded modules attempt to use related functions (ie. JSON functions from stdlib that call JSON), they fail because Puppet runs the custom function code within the Puppet::Pops::Loader::RubyFunctionInstantiator scope instead of top scope: 2020-03-18T00:00:29.762-05:00 ERROR [qtp802169583-480691] [puppetserver] Puppet Evaluation Error: Error while evaluating a Function Call, undefined method `pretty_generate' for Puppet::Pops::Loader::RubyFunctionInstantiator::JSON:Module (file: /etc/puppetlabs/code/environments/production/modules/npc_coreservices/manifests/components/cache_proxy/install.pp, line: 106, column: 22) on node pv20616cspgl01.npc.lan /etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/to_json_pretty.rb:36:in `to_json_pretty' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/dispatch.rb:60:in `invoke'
Jira (PDB-4675) Deadlock when creating/inserting into a new report partition
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4675 Deadlock when creating/inserting into a new report partition Change By: Nick Burgan Story Points: 3 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.350469.1584566547000.33959.1586370480360%40Atlassian.JIRA.
Jira (PDB-4678) PuppetDB cannot make DB connections when javax.net.ssl.trustStore is used
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4678 PuppetDB cannot make DB connections when javax.net.ssl.trustStore is used Change By: Nick Burgan Story Points: 2 1 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.351066.158509873.33960.1586370480403%40Atlassian.JIRA.
Jira (PDB-4644) If unset, resource-events-ttl should track report-ttl
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4644 If unset, resource-events-ttl should track report-ttl Change By: Nick Burgan Sprint: HA Team 2020-02-26, HA Team 2020-03-25, HA Team 2020-04-08 , HA Team 2020-04-22 (SS 4/15) 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.345022.1580840958000.33947.1586370240132%40Atlassian.JIRA.
Jira (PDB-4637) Lock out the puppetdb data user during migration
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4637 Lock out the puppetdb data user during migration Change By: Nick Burgan Sprint: HA Team 2020-03-11, HA Team 2020-03-25, HA Team 2020-04-08 , HA Team 2020-04-22 (SS 4/15) 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.343744.1580162942000.33948.1586370240175%40Atlassian.JIRA.
Jira (PDB-4676) Investigate OOM errors during the report partitioning migration
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4676 Investigate OOM errors during the report partitioning migration Change By: Nick Burgan Sprint: HA Team 2020-04-08 , HA Team 2020-04-22 (SS 4/15) 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.350711.1584735864000.33946.1586370240087%40Atlassian.JIRA.
Jira (PDB-4675) Deadlock when creating/inserting into a new report partition
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4675 Deadlock when creating/inserting into a new report partition Change By: Nick Burgan Sprint: HA Team 2020-04-08 , HA Team 2020-04-22 (SS 4/15) 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.350469.1584566547000.33949.1586370240219%40Atlassian.JIRA.
Jira (PDB-4678) PuppetDB cannot make DB connections when javax.net.ssl.trustStore is used
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4678 PuppetDB cannot make DB connections when javax.net.ssl.trustStore is used Change By: Nick Burgan Sprint: HA Team 2020-04-08 , HA Team 2020-04-22 (SS 4/15) 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.351066.158509873.33950.1586370240263%40Atlassian.JIRA.
Jira (FACT-2513) command line help shows flags incorrectly
Title: Message Title Sebastian Miclea commented on FACT-2513 Re: command line help shows flags incorrectly Hey Jesse Reynolds, just wanted to let you know that this has been fixed and released in 4.0.15. Thank you for checking out the new version! If you find any other issues, let us know! 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.353384.1585634122000.33868.1586369040047%40Atlassian.JIRA.
Jira (FACT-2535) Implement to_s on ResolvedFact
Title: Message Title Sebastian Miclea commented on FACT-2535 Re: Implement to_s on ResolvedFact Hey Steve Traylen, just as a short update, this was released with Facter 4.0.15. Thank you for testing the new version. If you find any other problems, let us know! 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.353994.1585839979000.33863.1586368920101%40Atlassian.JIRA.
Jira (PUP-10416) Comparing rpm package versions without epoch fails
Title: Message Title Luchian Nemes created an issue Puppet / PUP-10416 Comparing rpm package versions without epoch fails Issue Type: Bug Assignee: Unassigned Created: 2020/04/08 9:04 AM Priority: Normal Reporter: Luchian Nemes Desired Behavior: To succesfully do the version comparison: 3:1.0 < 1.2 Actual Behavior: Is not able to compare epoch 3 against missing epoch. Proposed solution: Currently, missing epoch is considered to be nil in the code. This should be instead treated as 0 when comparing versions. This case occurs when a package with a version containing epoch was already installed. Regarding this topic, version received in the :ensure field of the manifest should be stripped of epoch when installing packages (as yum at least seems to use epoch just for sorting the versions but will not find specific version when epoch is mentioned). Add Comment
Jira (FACT-2536) facter 4.x fails on Archlinux
Title: Message Title Andrei Filipovici commented on FACT-2536 Re: facter 4.x fails on Archlinux Hi Tim, We created a quick fix for you, available here: https://github.com/puppetlabs/facter-ng/pull/437 Sadly this led up to different problems, thus an official release with support for Arch Linux will arrive sometime in the near future. If anything changes, we'll let you know. 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.354178.1585993672000.33408.1586356560031%40Atlassian.JIRA.
Jira (PUP-10378) 'puppet resource service' does not return all active services on Ubuntu
Title: Message Title Michael Smith commented on PUP-10378 Re: 'puppet resource service' does not return all active services on Ubuntu Ok, if it doesn't seem feasible to identify this in Puppet that's fine. We can focus on fixing the service in PE. 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.350662.1584659329000.33389.1586354700034%40Atlassian.JIRA.
Jira (FACT-2538) Nil facts are shown when facter is called with --show-legacy
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2538 Nil facts are shown when facter is called with --show-legacy 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.354275.1586173838000.33341.1586346780037%40Atlassian.JIRA.
Jira (FACT-2542) refactor tests inside the spec/facter/facter_spec.rb file
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici Facter / FACT-2542 refactor tests inside the spec/facter/facter_spec.rb file Change By: Andrei Filipovici Assignee: Andrei Filipovici 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.354788.1586346307000.6.1586346360115%40Atlassian.JIRA.
Jira (FACT-2542) refactor tests inside the spec/facter/facter_spec.rb file
Title: Message Title Andrei Filipovici created an issue Facter / FACT-2542 refactor tests inside the spec/facter/facter_spec.rb file Issue Type: Task Assignee: Unassigned Created: 2020/04/08 4:45 AM Priority: Normal Reporter: Andrei Filipovici 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-2541) Add 'TYPE' constant for legacy facts
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2541 Add 'TYPE' constant for legacy facts Issue Type: Task Assignee: Unassigned Created: 2020/04/08 4:06 AM Priority: Normal Reporter: Oana Tanasoiu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2541) Add 'TYPE' constant for legacy facts
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2541 Add 'TYPE' constant for legacy facts 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.354786.1586343975000.33327.1586344020079%40Atlassian.JIRA.
Jira (FACT-2507) Update release documentation
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2507 Update release documentation 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.351400.1585313488000.33319.1586342580034%40Atlassian.JIRA.
Jira (PUP-10375) Latest version ensured for python packages is incorrect
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10375 Latest version ensured for python packages is incorrect Change By: Mihai Buzgau Story Points: 3 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.350599.158463166.33272.1586339220040%40Atlassian.JIRA.
Jira (PUP-10375) Latest version ensured for python packages is incorrect
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10375 Latest version ensured for python packages is incorrect Change By: Mihai Buzgau Sprint: PR NW - Triage 2020-04-15 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.350599.158463166.33273.1586339220099%40Atlassian.JIRA.
Jira (PUP-10394) puppet cannot handle same package name with different providers
Title: Message Title Ciprian Badescu commented on PUP-10394 Re: puppet cannot handle same package name with different providers probably caused by: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/package.rb#L312 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.351401.1585313546000.33268.1586338680655%40Atlassian.JIRA.
Jira (PUP-10395) Gem provider reports changes when using composed requirements
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10395 Gem provider reports changes when using composed requirements 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.351406.1585318227000.33253.1586338620041%40Atlassian.JIRA.
Jira (PUP-10395) Gem provider reports changes when using composed requirements
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10395 Gem provider reports changes when using composed requirements Change By: Mihai Buzgau Sprint: PR NW - Triage 2020-04-15 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.351406.1585318227000.33254.1586338620095%40Atlassian.JIRA.
Jira (PUP-10299) Add SemVerRange support to zypper package provider
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10299 Add SemVerRange support to zypper package provider Change By: Mihai Buzgau Sprint: PR - Triage, NW - 2020-03-04 , NW - 2020-04-15 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.346488.1582028971000.33249.1586338140030%40Atlassian.JIRA.
Jira (PUP-10410) package fails on openjdk with non-boolean status string
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10410 package fails on openjdk with non-boolean status string Change By: Mihai Buzgau Sprint: PR NW - Triage 2020-04-15 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.354183.1586042388000.33225.1586337060099%40Atlassian.JIRA.
Jira (PUP-10410) package fails on openjdk with non-boolean status string
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10410 package fails on openjdk with non-boolean status string Change By: Mihai Buzgau Story Points: 1 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.354183.1586042388000.33224.1586337060046%40Atlassian.JIRA.
Jira (PUP-10414) Windows service calls deprecated `puppet agent --configprint`
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10414 Windows service calls deprecated `puppet agent --configprint` Change By: Mihai Buzgau Sprint: PR NW - Triage 2020-04-15 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.354468.1586208728000.33209.1586336280183%40Atlassian.JIRA.
Jira (PUP-10414) Windows service calls deprecated `puppet agent --configprint`
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10414 Windows service calls deprecated `puppet agent --configprint` 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.354468.1586208728000.33208.1586336280140%40Atlassian.JIRA.
Jira (PUP-10322) Facter 4 debug logs don't use Puppet logger
Title: Message Title Sebastian Miclea updated an issue Puppet / PUP-10322 Facter 4 debug logs don't use Puppet logger Change By: Sebastian Miclea Release Notes Summary: Fixed the issue when enabling the facterng feature flag, the Facter debug logs were not forwarded to Puppet. 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.348049.1583162009000.33190.1586334780092%40Atlassian.JIRA.
Jira (PUP-10322) Facter 4 debug logs don't use Puppet logger
Title: Message Title Sebastian Miclea updated an issue Puppet / PUP-10322 Facter 4 debug logs don't use Puppet logger Change By: Sebastian Miclea Release Notes: Not Needed Bug Fix 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.348049.1583162009000.33188.1586334600040%40Atlassian.JIRA.
Jira (FACT-2540) Check what happens when external command fails, but exit code is 0
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2540 Check what happens when external command fails, but exit code is 0 Change By: Bogdan Irimie Reference tickethttps://tickets.puppetlabs.com/browse/PE-28690 Facter 3.x implementation[https://github.com/puppetlabs/facter/blob/master/lib/src/facts/aix/kernel_resolver.cc#L18] 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.354773.158633302.33166.1586333160038%40Atlassian.JIRA.
Jira (FACT-2540) Check what happens when external command fails, but exit code is 0
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2540 Check what happens when external command fails, but exit code is 0 Issue Type: Task Assignee: Unassigned Created: 2020/04/08 1:03 AM Priority: Normal Reporter: Bogdan Irimie Reference ticket https://tickets.puppetlabs.com/browse/PE-28690 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10378) 'puppet resource service' does not return all active services on Ubuntu
Title: Message Title Luchian Nemes commented on PUP-10378 Re: 'puppet resource service' does not return all active services on Ubuntu Michael Smith FYI above 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.350662.1584659329000.33160.1586332260030%40Atlassian.JIRA.
Jira (FACT-2539) POC All linux distributions inherit from Linux
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2539 POC All linux distributions inherit from Linux Issue Type: Task Assignee: Unassigned Created: 2020/04/08 12:36 AM Priority: Normal Reporter: Bogdan Irimie We should create a new level in os hierarchy names Linux and all linux distributions should inherit from it. If we don't know the name of the linux distribution, we will load the linux facts by default. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2517) Create Open3 wrapper for executing commands
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2517 Create Open3 wrapper for executing commands Change By: Bogdan Irimie The wrapper should capture the standard error, if present, and log in debug. 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.353906.1585810537000.33150.1586329260035%40Atlassian.JIRA.
Jira (FACT-2538) Nil facts are shown when facter is called with --show-legacy
Title: Message Title Sebastian Miclea assigned an issue to Unassigned Facter / FACT-2538 Nil facts are shown when facter is called with --show-legacy 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.354275.1586173838000.33133.1586327520033%40Atlassian.JIRA.
