Jira (PUP-10313) Selmodule provider fetch loaded modules performance
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10313 Selmodule provider fetch loaded modules performance Change By: Gheorghe Popescu Release Notes Summary: Improved performance on the selmodule providerThe `selmodule` provider was calling `/usr/sbin/semodule —list` one or twice per resource. This results in a heavy duplication of effort and increased apply time. Thanks https://github.com/montaguethomas for for implementing a cache which improves the performance. 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.347484.1582647231000.22396.1585294500031%40Atlassian.JIRA.
Jira (PUP-10313) Selmodule provider fetch loaded modules performance
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10313 Selmodule provider fetch loaded modules performance Change By: Gheorghe Popescu Release Notes: Enhancement 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.347484.1582647231000.22397.1585294560032%40Atlassian.JIRA.
Jira (PUP-10390) Ruby file gets loaded twice
Title: Message Title Luchian Nemes created an issue Puppet / PUP-10390 Ruby file gets loaded twice Issue Type: Improvement Assignee: Unassigned Created: 2020/03/27 1:57 AM Priority: Low Reporter: Luchian Nemes The provider/package/gem.rb file gets loaded twice. This prevents us from having constant variables without getting the following warnings at each run: /Users/luchi/repos/puppet/lib/puppet/provider/package/gem.rb:21: warning: already initialized constant MY_CONSTANT_VARIABLE /Users/luchi/repos/puppet/lib/puppet/provider/package/gem.rb:21: warning: previous definition of MY_CONSTANT_VARIABLE was here This happens due to the require done in provider/package/puppet_gem.rb and then loaded again in util/autoload.rb. This can be seen by putting a 'puts(caller)' in provider/package/gem.rb. Add Comment
Jira (PUP-10390) Ruby file gets loaded twice
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10390 Ruby file gets loaded twice Change By: Luchian Nemes The [provider/package/gem.rb|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/gem.rb] file gets loaded twice. This prevents us from having constant variables without getting the following warnings at each run:*/Users/luchi/repos/puppet/lib/puppet/provider/package/gem.rb:21: warning: already initialized constant MY_CONSTANT_VARIABLE**/Users/luchi/repos/puppet/lib/puppet/provider/package/gem.rb:21: warning: previous definition of MY_CONSTANT_VARIABLE was here*This happens due to the require done in [provider/package/puppet_gem.rb|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/puppet_gem.rb] and then loaded again in [util/autoload.rb|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/autoload.rb]. This can be seen by putting a 'puts(caller)' in [provider/package/gem.rb|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/gem.rb]. After fixing the issue, a refactoring should be done in [provider/package/gem.rb|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/gem.rb] to use (for better code readability):|GEM_VERSION = Puppet::Util::Package::Version::Gem||GEM_VERSION_RANGE = Puppet::Util::Package::Version::Range| Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10235) Support enable module with dnfmodule package provider
Title: Message Title Gabriel Nagy commented on PUP-10235 Re: Support enable module with dnfmodule package provider I did some investigation myself, and I found this PR on dnf which changes the behavior of dnf module install: https://github.com/rpm-software-management/dnf/pull/1427/ So it looks like prior to DNF version 4.2.8 you could run dnf module install on a module with no default profile, and it will silently enable it. With more recent versions, the command fails without enabling the stream. Apparently the previous behavior was misleading, since the install command wouldn't install any RPMs (see https://bugzilla.redhat.com/show_bug.cgi?id=1669527). This was a bit tricky to find out since on our test boxes we had an older version of DNF which didn't present this issue/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.342086.157904321.22412.1585300020026%40Atlassian.JIRA.
Jira (FACT-2502) Fix RSpec/ExpectInHook offences
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2502 Fix RSpec/ExpectInHook offences Issue Type: Task Assignee: Unassigned Created: 2020/03/27 4:01 AM Priority: Normal Reporter: 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.351389.1585306893000.22
Jira (FACT-2502) Fix RSpec/ExpectInHook offences
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2502 Fix RSpec/ExpectInHook offences 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.351389.1585306893000.22457.1585308060047%40Atlassian.JIRA.
Jira (FACT-2503) Fix RSpec/NamedSubject offences
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2503 Fix RSpec/NamedSubject offences Issue Type: Task Assignee: Oana Tanasoiu Created: 2020/03/27 4:32 AM Priority: Normal Reporter: 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.351391.1585308759000
Jira (PUP-10391) URI.escape is obsolete in Ruby 2.7
Title: Message Title Lucas Kanashiro created an issue Puppet / PUP-10391 URI.escape is obsolete in Ruby 2.7 Issue Type: Bug Assignee: Unassigned Created: 2020/03/27 5:05 AM Environment: Ubuntu Focal, ruby2.7, puppet 5.5.10. Priority: Normal Reporter: Lucas Kanashiro After using puppet 5.5.10 in Ubuntu with Ruby 2.7 I got the warning below: /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: warning: URI.escape is obsolete I also checked if it was fixed in the master branch but it doesn't: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util.rb#L463 Add Comment
Jira (PUP-10392) Version Range improvements for package providers
Title: Message Title Luchian Nemes created an issue Puppet / PUP-10392 Version Range improvements for package providers Issue Type: Improvement Assignee: Unassigned Created: 2020/03/27 5:11 AM Priority: Normal Reporter: Luchian Nemes During the implementation of version ranges for apt, yum, pip and gem providers, a couple of improvement ideas were raised. This ticket will most likely need to be split, based on any feedback received from the community and after deciding which of these topics can actually be achieved: whenever a version that satisfies the given range couldn't be found, the installation method shouldn't forward the input to the provider to handle the error, but instead puppet should stop there by raising the problem (execution time should improve, by avoiding double checking, and code complexity should also reduce for some providers, such as pip where there would be less translations through this improvement) range objects should become generic so that they can be created for any provider version (each provider version class should accept comparing version object to string, which the inside is parsed into a proper version object, so that range object creation doesn't require to know what type of versions will be compared), only once (instead of creating once for insync and then for installation also) and a lot sooner than inside the specific provider (somewhere in `lib/puppet/type/package.rb` was originally targeted but this needs to be further researched) through above implementation, checking if a string is a valid range can be reconsidered to remove all the error raisings caught in each provider ... other missed ideas can be further added
Jira (PUP-10392) Version Range improvements for package providers
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10392 Version Range improvements for package providers Change By: Luchian Nemes Priority: Normal Low 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.351395.1585311069000.22473.1585311300040%40Atlassian.JIRA.
Jira (PUP-10393) Use '**' to pass keyword arguments in Ruby 2.7
Title: Message Title Lucas Kanashiro created an issue Puppet / PUP-10393 Use '**' to pass keyword arguments in Ruby 2.7 Issue Type: Bug Assignee: Unassigned Created: 2020/03/27 5:16 AM Priority: Normal Reporter: Lucas Kanashiro Puppet Version: 5.5.10 (but it is not fixed in master branch also) Puppet Server Version: OS Name/Version: Ubuntu Focal. puppet 5.5.10, ruby2.7. Desired Behavior: No warning pops up when puppet is executed with Ruby 2.7. Actual Behavior: A warning is emitted here: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/file_system/file_impl.rb#L83 The '**' operator should be used to pass keyword arguments from now on. Add Comment This message was sent by Atlassian Jira
Jira (FACT-2504) Fix RSpec/MultipleExpectations
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2504 Fix RSpec/MultipleExpectations 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.351397.1585311983000.22478.1585312020071%40Atlassian.JIRA.
Jira (FACT-2504) Fix RSpec/MultipleExpectations
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2504 Fix RSpec/MultipleExpectations Issue Type: Task Assignee: Unassigned Created: 2020/03/27 5:26 AM Priority: Normal Reporter: 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.351397.1585311983000.224
Jira (FACT-2505) Define steps, processes and automations for releasing Facter 4
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2505 Define steps, processes and automations for releasing Facter 4 Issue Type: Epic Assignee: Unassigned Created: 2020/03/27 5:39 AM Priority: Normal Reporter: 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-bu
Jira (FACT-1950) Create Jenkins pipeline for acceptance tests
Title: Message Title Bogdan Irimie assigned an issue to Andrei Filipovici Facter / FACT-1950 Create Jenkins pipeline for acceptance tests Change By: Bogdan Irimie 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.316814.1563365598000.22481.1585312860087%40Atlassian.JIRA.
Jira (FACT-1950) Create Jenkins pipeline for acceptance tests
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1950 Create Jenkins pipeline for acceptance tests Change By: Bogdan Irimie Epic Link: FACT- 1947 2505 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.316814.1563365598000.22480.1585312860043%40Atlassian.JIRA.
Jira (FACT-2505) Define steps, processes and automations for releasing Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2505 Define steps, processes and automations for releasing Facter 4 Change By: Bogdan Irimie Sub-team: ghost Team/s: 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.351398.1585312793000.22483.1585313220031%40Atlassian.JIRA.
Jira (FACT-2506) Generate change-logs for release
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2506 Generate change-logs for release Issue Type: Task Assignee: Unassigned Created: 2020/03/27 5:49 AM Priority: Normal Reporter: Bogdan Irimie We should experiment with https://github.com/github-changelog-generator/github-changelog-generator for generating release change log. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2507) Update release documentation
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2507 Update release documentation Issue Type: Task Assignee: Unassigned Created: 2020/03/27 5:51 AM Priority: Normal Reporter: Bogdan Irimie Add: steps that need to be done in github (new release, with release notes) Jira release change-log generation Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10394) puppet cannot handle same package name with different providers
Title: Message Title Ciprian Badescu created an issue Puppet / PUP-10394 puppet cannot handle same package name with different providers Issue Type: Improvement Assignee: Unassigned Created: 2020/03/27 5:52 AM Priority: Normal Reporter: Ciprian Badescu While testing package providers I hit the case on Ubuntu14.04/x86_64 where the same package is present on both apt and pip providers. While individually the packages can be handled, there are issues on: output on `puppet resource package`, where only the default package gets listed having both packages in the same manifest root@sleek-clergymen:~# puppet resource package ssh-import-id ensure=present provider=pip package { 'ssh-import-id': ensure => '3.21', } root@sleek-clergymen:~# pip freeze | grep ssh-import-id
Jira (FACT-2270) Replace facter 2.x with facter 4.x in puppet as a gem
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2270 Replace facter 2.x with facter 4.x in puppet as a gem Change By: Bogdan Irimie Epic Status: To Do Done 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.341771.1578906124000.22493.1585314840036%40Atlassian.JIRA.
Jira (FACT-2508) How can we better interact with the community
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2508 How can we better interact with the community Issue Type: Epic Assignee: Unassigned Created: 2020/03/27 6:32 AM Priority: Normal Reporter: 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.351402.15
Jira (FACT-2509) Create CONTRIBUTING.md
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2509 Create CONTRIBUTING.md Issue Type: Task Assignee: Unassigned Created: 2020/03/27 6:35 AM Priority: Normal Reporter: Bogdan Irimie Write contributing guidance for community similar to https://github.com/puppetlabs/bolt/blob/master/CONTRIBUTING.md Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2509) Create CONTRIBUTING.md
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2509 Create CONTRIBUTING.md Change By: Bogdan Irimie Epic Link: FACT-2508 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.351403.1585316145000.22509.1585316220029%40Atlassian.JIRA.
Jira (FACT-2510) Start office hours
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2510 Start office hours 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.351404.1585316348000.22512.1585316400107%40Atlassian.JIRA.
Jira (FACT-2510) Start office hours
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2510 Start office hours Issue Type: Task Assignee: Unassigned Created: 2020/03/27 6:39 AM Priority: Normal Reporter: Bogdan Irimie Talk with Ben Ford regarding office hours for Facter 4. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10395) Gem provider reports changes when using composed requirements
Title: Message Title Gheorghe Popescu created an issue Puppet / PUP-10395 Gem provider reports changes when using composed requirements Issue Type: Task Affects Versions: PUP 5.5.18, PUP 6.14.0 Assignee: Unassigned Components: Types and Providers Created: 2020/03/27 7:10 AM Priority: Normal Reporter: Gheorghe Popescu Puppet Version: Puppet Server Version: OS Name/Version: Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful.
Jira (PUP-10395) Gem provider reports changes when using composed requirements
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10395 Gem provider reports changes when using composed requirements Change By: Gheorghe Popescu *Puppet Version: 5.5.x, master * *Puppet Server Version:* *OS Name/Version:* Describe your issue When installing packages and using the gem provider, if you pass in as much detail as possible… Describe steps to reproduce…*Desired Behavior the ensure a composed requirement('>1, <2') puppet will always report changes : * *Actual Behavior {code : *Please take puppet}box# cat a moment and attach any relevant log output and/or manifests . This will help us immensely when troubleshooting the issue.Examples pp package { 'color' : ensure => ">1, <2", provider => "gem" } Run box# puppet agent with apply a.pp -- test detailed - exitcodes Notice: Compiled catalog for worse - trace --debugRelevant sections of {{ swoop.delivery.puppetlabs.net in environment production in 0.41 seconds Notice: / var Stage[main] / log Main / puppetlabs Package[color] / puppetserver/puppetserver ensure: ensure changed ['1 . log}} or any applicable logs from the same directory 8', '0 . For more detailed information turn up the server logs by upping the log level in the server 1.0 ' s logback ] to '>1, <2' Notice: Applied catalog in 0 . xml 66 seconds box# echo $? 2 Relevant sections of configurations files ( box# puppet apply a . conf, hiera pp --detailed-exitcodes Notice: Compiled catalog for worse-swoop . conf delivery.puppetlabs.net in environment production in 0.41 seconds Notice: /Stage[main]/Main/Package[color]/ensure: ensure changed ['1.8' , Server ' s conf 0 . d 1.0'] to '>1 , defaults/sysconfig) <2' Notice: Applied catalog in 0.68 seconds box# echo $? 2 {code} For memory issues Seems like the Gem::Dependecy.new(https://github.com/ruby/ruby/blob/master/lib/rubygems/dependency.rb#L39) accepts a sparse argument and it can be used with server heap dumps an array but we are also helpful sending a string(https://github . com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/gem.rb#L130) Add Comment
Jira (PUP-10395) Gem provider reports changes when using composed requirements
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10395 Gem provider reports changes when using composed requirements Change By: Gheorghe Popescu *Puppet Version: 5.5.x, master* When installing packages and using the gem provider, if you pass in the ensure a composed requirement('>1, <2') puppet will always report changes:{code:puppet}box# cat a.pp package { 'color': ensure => ">1, <2", provider => "gem" }box# puppet apply a.pp --detailed-exitcodesNotice: Compiled catalog for worse-swoop.delivery.puppetlabs.net in environment production in 0.41 secondsNotice: /Stage[main]/Main/Package[color]/ensure: ensure changed ['1.8', '0.1.0'] to '>1, <2'Notice: Applied catalog in 0.66 seconds box# echo $? 2 box# puppet apply a.pp --detailed-exitcodesNotice: Compiled catalog for worse-swoop.delivery.puppetlabs.net in environment production in 0.41 seconds Notice: /Stage[main]/Main/Package[color]/ensure: ensure changed ['1.8', '0.1.0'] to '>1, <2'Notice: Applied catalog in 0.68 seconds box# echo $? 2{code}Seems like the Gem::Dependecy.new(https://github.com/ruby/ruby/blob/master/lib/rubygems/dependency.rb#L39) accepts a sparse argument and it can be used with an array but we are sending a string(https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/gem.rb#L130) Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10395) Gem provider reports changes when using composed requirements
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10395 Gem provider reports changes when using composed requirements Change By: Gheorghe Popescu *Puppet Version: 5.5.x, master* When installing packages and using the gem provider, if you pass in the ensure a composed requirement('>1, <2') puppet will always report changes:{code:puppet}box# cat a.pp package { 'color': ensure => ">1, <2", provider => "gem" }box# puppet apply a.pp --detailed-exitcodes Notice: Compiled catalog for worse-swoop.delivery.puppetlabs.net in environment production in 0.41 seconds Notice: /Stage[main]/Main/Package[color]/ensure: ensure changed ['1.8', '0.1.0'] to '>1, <2' Notice: Applied catalog in 0.66 seconds box# echo $? 2 box# puppet apply a.pp --detailed-exitcodes Notice: Compiled catalog for worse-swoop.delivery.puppetlabs.net in environment production in 0.41 secondsNotice: /Stage[main]/Main/Package[color]/ensure: ensure changed ['1.8', '0.1.0'] to '>1, <2' Notice: Applied catalog in 0.68 seconds box# echo $? 2{code}Seems like the Gem::Dependecy.new(https://github.com/ruby/ruby/blob/master/lib/rubygems/dependency.rb#L39) accepts a sparse argument and it can be used with an array but we are sending a string(https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/gem.rb#L130) Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10395) Gem provider reports changes when using composed requirements
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10395 Gem provider reports changes when using composed requirements Change By: Gheorghe Popescu Acceptance Criteria: I can use composed requirements(>x, 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.22543.1585318980380%40Atlassian.JIRA.
Jira (PUP-10395) Gem provider reports changes when using composed requirements
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10395 Gem provider reports changes when using composed requirements Change By: Gheorghe Popescu *Puppet Version: 5.5.x, master* When installing packages and using the gem provider, if you pass in the ensure a composed requirement('> 1 x , < 2 y ') puppet will always report changes:{code:puppet}box# cat a.pp package { 'color': ensure => ">1, <2", provider => "gem" }box# puppet apply a.pp --detailed-exitcodes Notice: Compiled catalog for worse-swoop.delivery.puppetlabs.net in environment production in 0.41 seconds Notice: /Stage[main]/Main/Package[color]/ensure: ensure changed ['1.8', '0.1.0'] to '>1, <2' Notice: Applied catalog in 0.66 seconds box# echo $? 2 box# puppet apply a.pp --detailed-exitcodes Notice: Compiled catalog for worse-swoop.delivery.puppetlabs.net in environment production in 0.41 secondsNotice: /Stage[main]/Main/Package[color]/ensure: ensure changed ['1.8', '0.1.0'] to '>1, <2' Notice: Applied catalog in 0.68 seconds box# echo $? 2{code}Seems like the Gem::Dependecy.new(https://github.com/ruby/ruby/blob/master/lib/rubygems/dependency.rb#L39) accepts a sparse argument and it can be used with an array but we are sending a string (https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/gem.rb#L130) Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4625) puppetdb ssl connection to postgresql broken
Title: Message Title Vincent Magnin commented on PDB-4625 Re: puppetdb ssl connection to postgresql broken Hello, I was facing the same issue on a fresh install of puppetdb 6.9.2 on Centos8, with postgresql 10.6 Following https://tickets.puppetlabs.com/browse/PDB-4579 I've done the workaround provided here : https://tickets.puppetlabs.com/browse/PDB-4678 Which has solved the issue, but need to remove the java keystore until postgresql driver rework (according comment on PDB-4579) Regards 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.342311.1579141305000.22572.1585322100031%40Atlassian.JIRA.
Jira (PUP-10396) Mechanism that allows one OS to inherit facts from another OS
Title: Message Title Bogdan Irimie created an issue Puppet / PUP-10396 Mechanism that allows one OS to inherit facts from another OS Issue Type: Epic Assignee: Unassigned Created: 2020/03/27 8:26 AM Priority: Normal Reporter: 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-bug
Jira (PUP-10235) Support enable module with dnfmodule package provider
Title: Message Title Jens Almer commented on PUP-10235 Re: Support enable module with dnfmodule package provider Hey Gabriel, I appreciate your work on this! I never noticed the fallback behavior, but I can confirm that is correct. My assumption after observing the lack of idempotency was that it was failing to enable the module. The open PR should meet my needs. Takk! --Jens On Fri, Mar 27, 2020 at 6:28 AM Gabriel Nagy (Jira) < 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.342086.157904321.22671.1585327380271%40Atlassian.JIRA.
Jira (PDB-4675) Deadlock when creating/inserting into a new report partition
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4675 Deadlock when creating/inserting into a new report partition Change By: Austin Blatt Assignee: Austin Blatt 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.22684.1585327680571%40Atlassian.JIRA.
Jira (PUP-10235) Support enable module with dnfmodule package provider
Title: Message Title Jens Almer commented on PUP-10235 Re: Support enable module with dnfmodule package provider I missed your comment about the DNF behavior change. Good find! 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.342086.157904321.22691.1585328220026%40Atlassian.JIRA.
Jira (FACT-2489) no resolver for external facts file error for os-specific facts
Title: Message Title Thomas Kishel commented on FACT-2489 Re: no resolver for external facts file error for os-specific facts Yes, wintel_flexera_version can be ignored. This changes the statistics the the PE Console Overview, which some users depend on for status. How could we deliver just this 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.350967.1585072495000.22712.1585328820026%40Atlassian.JIRA.
Jira (PUP-10397) Remove facts and vars from ScriptCompiler scope
Title: Message Title Tom Beech created an issue Puppet / PUP-10397 Remove facts and vars from ScriptCompiler scope Issue Type: Task Assignee: Tom Beech Created: 2020/03/27 10:09 AM Priority: Normal Reporter: Tom Beech As part of a Bolt ticket https://github.com/puppetlabs/bolt/issues/1403 we would like to remove facts and vars from the ScriptCompiler scope. Since it does not make sense for plans to have a concept of facts or vars, these fields should be removed from the ScriptCompiler's scope. This will disable the use of interpolations when performing lookups in plans outside of apply blocks. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2489) no resolver for external facts file error for os-specific facts
Title: Message Title Ciprian Badescu commented on FACT-2489 Re: no resolver for external facts file error for os-specific facts not easy to get only this fix, but the correction should be available in the latest puppet5 nightly and the next puppet6 nightly. 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.350967.1585072495000.22828.1585332960043%40Atlassian.JIRA.
Jira (PUP-10398) Installing/upgrading multiple packages at once
Title: Message Title Corey Benefrayim created an issue Puppet / PUP-10398 Installing/upgrading multiple packages at once Issue Type: Improvement Assignee: Unassigned Created: 2020/03/27 11:32 AM Priority: Normal Reporter: Corey Benefrayim Ran into an issue with a node that has multiple architectures of a package installed (libcurl.i686 and libcurl.x86_64.) When trying to use puppet to handle the upgrade of the package, it failed because the package resource handled the updates one at a time. This appears to be a limitation of yum as the packages must be the exact same revision. This can be circumvented by having both package names in the same yum command: yum install libcurl.x86_64 libcurl.i686 I was able to circumvent this with the following class definition: class update_libcurl { exec { 'yum_update_libcurl': command => 'yum install libcurl.x86_64 libcurl.i686 -y', path => '/usr/bin/', } } * Please see Zendesk Support tab for further comments and attachments. Add Comment
Jira (PUP-10398) Installing/upgrading multiple packages at once
Title: Message Title Austin Boyd updated an issue Puppet / PUP-10398 Installing/upgrading multiple packages at once Change By: Austin Boyd Labels: jira_escalated 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.351443.1585333932000.22846.1585333980367%40Atlassian.JIRA.
Jira (PUP-10398) Installing/upgrading multiple packages at once
Title: Message Title Austin Boyd updated an issue Puppet / PUP-10398 Installing/upgrading multiple packages at once Change By: Austin Boyd Zendesk Ticket Count: 1 Zendesk Ticket IDs: 38615 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.351443.1585333932000.22847.1585333980411%40Atlassian.JIRA.
Jira (PUP-10398) Installing/upgrading multiple architectures of a package.
Title: Message Title Corey Benefrayim updated an issue Puppet / PUP-10398 Installing/upgrading multiple architectures of a package. Change By: Corey Benefrayim Summary: Installing/upgrading multiple packages at once architectures of a package. 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.351443.1585333932000.22848.1585334040033%40Atlassian.JIRA.
Jira (PUP-10393) Use '**' to pass keyword arguments in Ruby 2.7
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10393 Use '**' to pass keyword arguments in Ruby 2.7 Change By: Josh Cooper 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.351396.1585311394000.23088.1585343580095%40Atlassian.JIRA.
Jira (PUP-10238) Change strict_hostname_checking to true
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10238 Change strict_hostname_checking to true Change By: Josh Cooper Epic Link: PUP-9120 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.342589.1579286482000.23131.1585344720031%40Atlassian.JIRA.
Jira (PUP-10397) Remove facts and vars from ScriptCompiler scope
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10397 Remove facts and vars from ScriptCompiler scope Change By: Josh Cooper Team: Bolt 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.351426.1585328999000.23140.1585344900038%40Atlassian.JIRA.
Jira (PUP-10398) Installing/upgrading multiple architectures of a package.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10398 Installing/upgrading multiple architectures of a package. Change By: Josh Cooper Ran into an issue with a node that has multiple architectures of a package installed (libcurl.i686 and libcurl.x86_64.)When trying to use puppet to handle the upgrade of the package, it failed because the package resource handled the updates one at a time. This appears to be a limitation of yum as the packages must be the exact same revision.This can be circumvented by having both package names in the same yum command: {noformat} yum install libcurl.x86_64 libcurl.i686 {noformat} I was able to circumvent this with the following class definition: {code:puppet} class update_libcurl {exec { 'yum_update_libcurl': command => 'yum install libcurl.x86_64 libcurl.i686 -y', path => '/usr/bin/',}} {code} ~* Please see Zendesk Support tab for further comments and attachments.~ Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10398) Installing/upgrading multiple architectures of a package.
Title: Message Title Josh Cooper commented on PUP-10398 Re: Installing/upgrading multiple architectures of a package. This is a duplicate of PUP-1061. It's not currently possible to install multiple packages at once using the package type. As a result puppet can't install packages that have circular dependencies like 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.351443.1585333932000.23148.1585345260063%40Atlassian.JIRA.
Jira (PUP-10387) Remove puppet module build, generate and search actions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10387 Remove puppet module build, generate and search actions Change By: Josh Cooper Team: Coremunity 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.350961.1585070066000.23150.1585345260163%40Atlassian.JIRA.
Jira (PUP-10398) Installing/upgrading multiple architectures of a package.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10398 Installing/upgrading multiple architectures of a package. Change By: Josh Cooper 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.351443.1585333932000.23149.1585345260119%40Atlassian.JIRA.
Jira (PUP-10386) Remove status application
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10386 Remove status application Change By: Josh Cooper Team: Coremunity 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.350960.1585070005000.23151.1585345260207%40Atlassian.JIRA.
Jira (PUP-10394) puppet cannot handle same package name with different providers
Title: Message Title Josh Cooper commented on PUP-10394 Re: puppet cannot handle same package name with different providers This issue should already be supported, see PUP-1073 In PUP-3721 (fixed in 6.13.0), puppet resource package now emits the provider that was used, to avoid naming collisions. You can achieve the same effect in 5.5.x using puppet resource package --param provider. In order to manage two packages with the same name, you have to specify the provider for both resources, which I think is why this fails: root@sleek-clergymen:~# cat a.pp package { 'ssh-import-id': ensure => '3.21', provider => 'pip', } package { 'ssh-import-id': ensure => '3.21-0ubuntu1', } I don't think puppet will generate the composite key for the resource if the provider is unspecified, and it picks the most suitable provider. See also https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/package/common_package_name_in_different_providers.rb Add Comment This message was sent by Atl
Jira (PUP-5539) circular dependent RPM packages can't be uninstalled
Title: Message Title Josh Cooper commented on PUP-5539 Re: circular dependent RPM packages can't be uninstalled Reopened 4 years later :facepalm: 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.106812.1448282237000.23178.1585345740040%40Atlassian.JIRA.
Jira (PUP-5539) circular dependent RPM packages can't be uninstalled
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5539 circular dependent RPM packages can't be uninstalled Change By: Josh Cooper 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.106812.1448282237000.23179.1585345740083%40Atlassian.JIRA.
Jira (PUP-10391) URI.escape is obsolete in Ruby 2.7
Title: Message Title Josh Cooper commented on PUP-10391 Re: URI.escape is obsolete in Ruby 2.7 We really just need to move to using Addressable. Assigning to Coremunity as we've been working on the rewriting the client networking code. 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.351394.1585310712000.23180.1585345800025%40Atlassian.JIRA.
Jira (PUP-10391) URI.escape is obsolete in Ruby 2.7
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10391 URI.escape is obsolete in Ruby 2.7 Change By: Josh Cooper Team: Coremunity 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.351394.1585310712000.23181.1585345860028%40Atlassian.JIRA.
Jira (PUP-10394) puppet cannot handle same package name with different providers
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10394 puppet cannot handle same package name with different providers Change By: Josh Cooper 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.351401.1585313546000.23184.1585345980133%40Atlassian.JIRA.
Jira (FACT-2511) Facter is trying to create a log file inside the gem installation path
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2511 Facter is trying to create a log file inside the gem installation path Issue Type: Bug Assignee: Unassigned Attachments: Untitled Created: 2020/03/27 3:00 PM Priority: Normal Reporter: Bogdan Irimie Jesse Scott has reported: PDK nightly builds just started picking up Facter 4 and our acceptance tests are failing in the scenario where the PDK package has been installed on a system as root but then an unprivileged user is running commands. It appears Facter is trying to create a log file inside the gem installation path by default. The problem seams to be provoked by https://github.com/puppetlabs/facter-ng/blob/master/lib/framework/logging/logger.rb#L9 is where that default log file path seems to be defined Add Comment
Jira (FACT-2511) Facter is trying to create a log file inside the gem installation path
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2511 Facter is trying to create a log file inside the gem installation path 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.351452.1585346432000.23205.1585346580077%40Atlassian.JIRA.
Jira (PUP-10399) Error: wrong number of arguments (given 2, expected 1) Deferred fucntion
Title: Message Title Lucas Young created an issue Puppet / PUP-10399 Error: wrong number of arguments (given 2, expected 1) Deferred fucntion Issue Type: Bug Assignee: Unassigned Created: 2020/03/27 3:32 PM Priority: Normal Reporter: Lucas Young Puppet Version: Puppet 6.10.2 Puppet Server Version: 2019.2.2 OS Name/Version: Ubuntu 16.04 Actual Behavior: When setting up a deferred function if a difference number of arguments are passed into the dispatch declaration versus the actual method a Puppet run will generate the following error: "Error: Failed to apply catalog: wrong number of arguments (given 2, expected 1)" The issue is that none of the file / line number information is returned as part of the error message above, offering no trace back to the origination of the error in the code base. Code example: dispatch :example do param 'String', :stuff optional_param 'String', :morestuff end def example(stuff)
Jira (PUP-10399) Error: wrong number of arguments (given 2, expected 1) Deferred function doesn't return file / line number
Title: Message Title Lucas Young updated an issue Puppet / PUP-10399 Error: wrong number of arguments (given 2, expected 1) Deferred function doesn't return file / line number Change By: Lucas Young Summary: Error: wrong number of arguments (given 2, expected 1) Deferred fucntion function doesn't return file / line number 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.351455.1585348372000.23268.1585348440032%40Atlassian.JIRA.
Jira (PUP-10399) Error: wrong number of arguments (given 2, expected 1) Deferred function doesn't return file / line number
Title: Message Title Lucas Young updated an issue Puppet / PUP-10399 Error: wrong number of arguments (given 2, expected 1) Deferred function doesn't return file / line number Change By: Lucas Young *Puppet Version: Puppet 6.10.2* *Puppet Server Version: 2019.2.2* *OS Name/Version: Ubuntu 16.04**+Actual Behavior:+* When setting up a deferred function if a difference number of arguments are passed into the dispatch declaration versus the actual method a Puppet run will generate the following error: "*Error: Failed to apply catalog: wrong number of arguments (given 2, expected 1)*"The issue is that none of the file / line number information is returned as part of the error message above, offering no trace back to the origination of the error in the code base. +*Code example:*+ {code:java} dispatch :example do param 'String', :stuff optional_param 'String', :morestuffenddef example(stuff) return stuff + 1end {code} When the same code is ran and it is not a Deferred function, a file / line number is included in that error message. *+Desired behavior:+* Generate an error message with a line / file indication: "Error: Failed tp apply catalog, wrong number of arguments (given 2, expected 1) (file: /home/test_user/Working/custom_function_repro/modules/test_module/manifests/init.pp, line: 2, column: 8)" Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10366) 5.5.17 agents fail on interval runs
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10366 5.5.17 agents fail on interval runs Change By: Josh Cooper Fix Version/s: PUP 5.5.19 Fix Version/s: PUP 5.5.20 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.349295.1583914641000.23286.1585351260049%40Atlassian.JIRA.