Jira (FACT-2583) Exclude spec/framework from RSpec/FilePath
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2583 Exclude spec/framework from RSpec/FilePath Issue Type: Task Assignee: Unassigned Created: 2020/04/28 12:20 AM Priority: Normal Reporter: Bogdan Irimie Until we change the placement of all files in the project to match their namespace we should exclude everything that is under spec/framework from RSpec/FilePath https://github.com/puppetlabs/facter-ng/pull/470/files#r416021764 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 Claire Cadman commented on PUP-10235 Re: Support enable module with dnfmodule package provider Gabriel Nagy will do! 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.48548.1588060080085%40Atlassian.JIRA.
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 For everyone watching this issue, due to the additional use cases of DNF modules compared to other package providers, and because we want to implement a most logical way of managing a DNF module (enabling, disabling, installing, removing, resetting), we are not going to document this feature yet. This means that the current implementation is subject to change, depending on how PUP-10419 is implemented. Thanks for the understanding, and we apologize for any inconvenience this might cause. 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.48554.1588061820028%40Atlassian.JIRA.
Jira (PDB-4513) puppetserver fails to connect to puppetdb 6.6.0
Title: Message Title Yvan Broccard commented on PDB-4513 Re: puppetserver fails to connect to puppetdb 6.6.0 I had exactly the same problem, upgrading from PuppetDB 6.5 to 6.9. After strugging with this for days and reproducing the problem with the Ciphers, I solved the problem in upgrading to Java 11, and then ... poof, no more problem. No need to fight with the ciphers if you use a more recent version of Java. It seems. Maybe a line in the release note about the version of java would have helped. I was using java-1.7.0-openjdk. Now I've replaced it with java-11-openjdk Cheers Yvan 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.326149.1569370509000.48562.158806525%40Atlassian.JIRA.
Jira (PDB-4606) Partition the reports table
Title: Message Title Claire Cadman commented on PDB-4606 Re: Partition the reports table Margaret Lee will do! 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.340126.1576694351000.48599.1588069080034%40Atlassian.JIRA.
Jira (FACT-2584) Puppet 6 on Ubuntu 20.04 missing $::is_virtual fact
Title: Message Title Mihai Buzgau moved an issue Facter / FACT-2584 Puppet 6 on Ubuntu 20.04 missing $::is_virtual fact Change By: Mihai Buzgau Key: PUP FACT - 10468 2584 Project: Puppet Facter 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.356817.1587845996000.48601.1588069140100%40Atlassian.JIRA.
Jira (FACT-2584) Puppet 6 on Ubuntu 20.04 missing $::is_virtual fact
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2584 Puppet 6 on Ubuntu 20.04 missing $::is_virtual fact Change By: Mihai Buzgau Sub-team: 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.356817.1587845996000.48602.1588069200031%40Atlassian.JIRA.
Jira (FACT-2584) Puppet 6 on Ubuntu 20.04 missing $::is_virtual fact
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2584 Puppet 6 on Ubuntu 20.04 missing $::is_virtual fact Change By: Bogdan Irimie Priority: Normal High 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.356817.1587845996000.48612.1588070760029%40Atlassian.JIRA.
Jira (FACT-2582) external data yaml facts don't load Time values
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2582 external data yaml facts don't load Time values Change By: Bogdan Irimie Priority: Normal High 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.356951.1588050537000.48613.1588070820029%40Atlassian.JIRA.
Jira (FACT-2582) external data yaml facts don't load Time values
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2582 external data yaml facts don't load Time values 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.356951.1588050537000.48615.1588070940103%40Atlassian.JIRA.
Jira (FACT-2584) Puppet 6 on Ubuntu 20.04 missing $::is_virtual fact
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2584 Puppet 6 on Ubuntu 20.04 missing $::is_virtual fact 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.356817.1587845996000.48614.1588070940048%40Atlassian.JIRA.
Jira (PUP-10295) Add SemVerRange support to gem package provider
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10295 Add SemVerRange support to gem package provider Change By: Claire Cadman Labels: doc_reviewed 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.346484.1582028683000.48618.1588071240031%40Atlassian.JIRA.
Jira (PDB-4513) puppetserver fails to connect to puppetdb 6.6.0
Title: Message Title Yvan Broccard updated an issue PuppetDB / PDB-4513 puppetserver fails to connect to puppetdb 6.6.0 Change By: Yvan Broccard Comment: I had exactly the same problem, upgrading from PuppetDB 6.5 to 6.9.After strugging with this for days and reproducing the problem with the Ciphers, I solved the problem in upgrading to Java 11, and then ... poof, no more problem. No need to fight with the ciphers if you use a more recent version of Java. It seems. Maybe a line in the release note about the version of java would have helped.I was using java-1.7.0-openjdk.Now I've replaced it with java-11-openjdkCheersYvan 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.326149.1569370509000.48656.1588077660042%40Atlassian.JIRA.
Jira (FACT-2545) AIX kernel resovler redirects stderr to stdout, which breaks facts on OS errors
Title: Message Title Claire Cadman updated an issue Facter / FACT-2545 AIX kernel resovler redirects stderr to stdout, which breaks facts on OS errors Change By: Claire Cadman Labels: doc_reviewed 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.355220.1586513484000.48665.1588078560035%40Atlassian.JIRA.
Jira (FACT-2544) Move cached-custom-facts to a new section in facter.conf
Title: Message Title Claire Cadman updated an issue Facter / FACT-2544 Move cached-custom-facts to a new section in facter.conf Change By: Claire Cadman Labels: doc_reviewed 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.355219.1586506973000.48666.1588078620027%40Atlassian.JIRA.
Jira (FACT-2171) Fix for tests/options/verbose.rb
Title: Message Title Claire Cadman updated an issue Facter / FACT-2171 Fix for tests/options/verbose.rb Change By: Claire Cadman Labels: doc_reviewed 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.337971.1575556609000.48669.1588078740155%40Atlassian.JIRA.
Jira (FACT-2489) no resolver for external facts file error for os-specific facts
Title: Message Title Claire Cadman updated an issue Facter / FACT-2489 no resolver for external facts file error for os-specific facts Change By: Claire Cadman Labels: doc_reviewed 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.350967.1585072495000.48668.1588078740111%40Atlassian.JIRA.
Jira (FACT-2537) Not compatible with leatherman >= 1.0.0
Title: Message Title Claire Cadman updated an issue Facter / FACT-2537 Not compatible with leatherman >= 1.0.0 Change By: Claire Cadman Labels: doc_reviewed 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.354200.1586117199000.48667.1588078740058%40Atlassian.JIRA.
Jira (FACT-1575) Add the ability to cache and block the output of custom facts
Title: Message Title Claire Cadman updated an issue Facter / FACT-1575 Add the ability to cache and block the output of custom facts Change By: Claire Cadman Labels: blocklist cache doc_reviewed 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.176225.1487804791000.48672.1588078860030%40Atlassian.JIRA.
Jira (FACT-2585) Mountpoints fact returns ASCI-8BIT instead of UTF-8 in some cases
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2585 Mountpoints fact returns ASCI-8BIT instead of UTF-8 in some cases Issue Type: Bug Assignee: Unassigned Created: 2020/04/28 5:59 AM Priority: Normal Reporter: Bogdan Irimie When TimeMachine is running on mac, the mountpoints fact returns ASCI-8BIT instead of UTF-8 and the JSON parser fails to parse the output. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2585) Mountpoints fact returns ASCI-8BIT instead of UTF-8 in some cases
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2585 Mountpoints fact returns ASCI-8BIT instead of UTF-8 in some cases 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.356990.1588078785000.48671.1588078800144%40Atlassian.JIRA.
Jira (PUP-8051) puppet agent option to wait for lock
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-8051 puppet agent option to wait for lock Change By: Mihai Buzgau Sprint: PR - Triage, NW - 2020-04-01, NW - 2020-04-15 , NW - 2020-05-13 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.216234.1507933383000.48697.1588080720043%40Atlassian.JIRA.
Jira (PUP-10433) Zypper provider doesn't recognize --no-gpg-checks as global option
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10433 Zypper provider doesn't recognize --no-gpg-checks as global option Change By: Mihai Buzgau Sprint: NW - 2020-05-13 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.356395.1587577044000.48700.1588080900026%40Atlassian.JIRA.
Jira (FACT-2586) Fix GitHub actions test runs to match those on CI pipeline
Title: Message Title Andrei Filipovici created an issue Facter / FACT-2586 Fix GitHub actions test runs to match those on CI pipeline Issue Type: New Feature Assignee: Andrei Filipovici Created: 2020/04/28 6:36 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 https://groups.google.com
Jira (PDB-4635) puppetdb_avg_mem larger than baseline values
Title: Message Title John Duarte commented on PDB-4635 Re: puppetdb_avg_mem larger than baseline values For the performance comparison run of week 2020-04-27, this tolerance failed when testing recent PE master build (2019.7.0-rc1-15-gcd7efbb) to the LTS baseline (but not STS). 2019.7.0-rc1-15-gcd7efbb 2018.1.14 comparison: Result 'process_puppetdb_avg_mem' is outside tolerances: baseline: 730893; result: 888628; variance: 21.58% 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.343321.1579814655000.48737.1588084140041%40Atlassian.JIRA.
Jira (PUP-10469) Portage package provider doesn't work on Gentoo-based distributions
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10469 Portage package provider doesn't work on Gentoo-based distributions Change By: Mihai Buzgau Sprint: NW - 2020-05-13 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.356838.1587989378000.48739.1588084740043%40Atlassian.JIRA.
Jira (PUP-10443) Zypper package downgrade not working
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10443 Zypper package downgrade not working Change By: Mihai Buzgau Sprint: PR - Triage 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.356662.1587731819000.48740.1588084800035%40Atlassian.JIRA.
Jira (FACT-2569) Create a Github actions jobs that runs acceptance tests from Facter repo
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2569 Create a Github actions jobs that runs acceptance tests from Facter repo Change By: Andrei Filipovici Summary: Create a Github actions jobs that clones runs acceptance tests from Facter repo 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.356335.1587549567000.48759.1588085700026%40Atlassian.JIRA.
Jira (PUP-10476) Update Puppet's PAL API to fulfill bolt use cases
Title: Message Title Sean McDonald created an issue Puppet / PUP-10476 Update Puppet's PAL API to fulfill bolt use cases Issue Type: Task Assignee: Sean McDonald Created: 2020/04/28 8:01 AM Priority: Normal Reporter: Sean McDonald Update the PAL implementation to support newer use cases in bolt. There are a few cases in bolt's code where we are calling private functions in the compile layer to override some settings. At least two examples: one when filtering variables and another when evaluating to get node definitions Bolt also overrides some puppet settings, like rich data. The PAL layer in puppet should be updated to handle these cases and have sane defaults, such that we don't need to call private or internal functions in bolt (or PE when it's using bolt) or update puppet settings to compile correctly. Add Comment
Jira (PUP-10476) Update Puppet's PAL API to fulfill bolt use cases
Title: Message Title Sean McDonald commented on PUP-10476 Re: Update Puppet's PAL API to fulfill bolt use cases This is assigned to me for now. This work was spawned from conversations around the compile API in puppetserver and changes we needed to support apply blocks in plans: https://github.com/puppetlabs/puppetserver/pull/2329#discussion_r416030694 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.357007.1588086087000.48776.1588087320024%40Atlassian.JIRA.
Jira (PUP-10292) external trusted data is executed for file_content requests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10292 external trusted data is executed for file_content requests Change By: Josh Cooper Sprint: Coremunity Hopper 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.346028.1581515567000.48780.1588087860103%40Atlassian.JIRA.
Jira (PUP-10292) external trusted data is executed for file_content requests
Title: Message Title Josh Cooper assigned an issue to Reid Vandewiele Puppet / PUP-10292 external trusted data is executed for file_content requests Change By: Josh Cooper Assignee: Reid Vandewiele 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.346028.1581515567000.48779.1588087860043%40Atlassian.JIRA.
Jira (PUP-9096) Puppet 6.y Deprecations
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9096 Puppet 6.y Deprecations Change By: Josh Cooper Team/s: 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.273793.1535733648000.48811.1588089060047%40Atlassian.JIRA.
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title Josh Cooper commented on PUP-10428 Re: Puppet parser only consider first element of array for properties in custom provider Thanks for letting us know Dan33l 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.356064.1587390623000.48814.1588089120079%40Atlassian.JIRA.
Jira (PUP-10407) "Unable to set ownership" error with logdest on agents running as root
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10407 "Unable to set ownership" error with logdest on agents running as root Change By: Josh Cooper Sprint: Coremunity Hopper 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.353908.1585812512000.48825.1588089180484%40Atlassian.JIRA.
Jira (PUP-10407) "Unable to set ownership" error with logdest on agents running as root
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-10407 "Unable to set ownership" error with logdest on agents running as root Change By: Josh Cooper Assignee: Josh Cooper 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.353908.1585812512000.48843.1588090020033%40Atlassian.JIRA.
Jira (PUP-1913) Puppet user resource should respect the forcelocal option
Title: Message Title Josh Cooper commented on PUP-1913 Re: Puppet user resource should respect the forcelocal option The functionality described in this ticket was implemented (see PUP-8470, PUP-9195, PUP-10169), so I'm closing this ticket. Please reopen if something is missing. 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.28357.1394483936000.48848.1588090500060%40Atlassian.JIRA.
Jira (FACT-2587) Puppet facts missing on facter 3.10.0 with OSP 6.13.0
Title: Message Title Lee Lowder created an issue Facter / FACT-2587 Puppet facts missing on facter 3.10.0 with OSP 6.13.0 Issue Type: Bug Affects Versions: FACT 3.10.0 Assignee: Unassigned Created: 2020/04/28 9:58 AM Priority: Normal Reporter: Lee Lowder When running `facter -p` (with or without sudo) the following warning is mentioned: WARN puppetlabs.facter - Could not load puppet; some facts may be unavailable: cannot load such file – puppet This is happening with open source puppet 6.13.0 on Ubuntu 18.04 systems. Add Comment
Jira (PDB-3832) puppetdb module config.ini mgmt should be in sync with rpm
Title: Message Title Morgan Rhodes commented on PDB-3832 Re: puppetdb module config.ini mgmt should be in sync with rpm PR is up to fix this, but it's blocked on https://github.com/puppetlabs/ezbake/pull/571 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.235342.1517910172000.49000.1588093140047%40Atlassian.JIRA.
Jira (PUP-10475) Remove Puppet::Util::Yaml.load_file
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10475 Remove Puppet::Util::Yaml.load_file 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.356948.1588032733000.49002.1588093200157%40Atlassian.JIRA.
Jira (PUP-10474) Remove deprecated Puppet::Resource methods
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10474 Remove deprecated Puppet::Resource methods 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.356947.158803264.49003.1588093200199%40Atlassian.JIRA.
Jira (PUP-10472) Remove Puppet.define_settings
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10472 Remove Puppet.define_settings 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.356936.1588031208000.49005.1588093200320%40Atlassian.JIRA.
Jira (PUP-10473) Remove legacy auth.conf support
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10473 Remove legacy auth.conf support Change By: Josh Cooper Team: Froyo 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.356946.1588032295000.49004.1588093200243%40Atlassian.JIRA.
Jira (PUP-10476) Update Puppet's PAL API to fulfill bolt use cases
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10476 Update Puppet's PAL API to fulfill bolt use cases Change By: Josh Cooper Team: Skeletor 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.357007.1588086087000.49006.1588093260027%40Atlassian.JIRA.
Jira (PUP-7197) make type aliases from modules available on the agent
Title: Message Title Lee Lowder commented on PUP-7197 Re: make type aliases from modules available on the agent Another area where having type aliases (and puppet language functions) plugin sync are in the use of deferred functions and deferred templates. Say I have an epp template that takes two parameters - a String for the password, and an Stdlib::Absolutepath for some config file or a binary. If I use Deferred on the template so I can have the password come out of vault or some other secret management tool, then because type aliases are not pluginsnced, when the template is rendered on the agent side, I get an error about unknown type Stdlib::Absolutepath. The same sort of thing happens if I try to deferr a puppet language based function - something that the docs have been pushing people very hard to start using over the last few years and versions. 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.174775.1486632721000.49037.1588094640026%40Atlassian.JIRA.
Jira (PUP-3922) Preserve modulepath structure during pluginsync
Title: Message Title Trevor Vaughan commented on PUP-3922 Re: Preserve modulepath structure during pluginsync Issues with things like client side namespacing have been problematic in the module space for years. Honestly, I think that everything should be namespaced at this point and that it should all be completely unambiguous where possible. In my opinion, one of the main issues is that this causes users to try modules form the Forge but either reject them, or fork them, due to namespace collisions. Fixing this issue would be a boon for the overall reusability of the module space in general. 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.65973.1422487314000.49057.1588095180427%40Atlassian.JIRA.
Jira (FACT-2588) ipa_facts : does not extract info from sssd.conf
Title: Message Title
Han Boetes created an issue
Facter / FACT-2588
ipa_facts : does not extract info from sssd.conf
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/04/28 12:54 PM
Environment:
Priority:
Normal
Reporter:
Han Boetes
This problem is related to: https://projects.theforeman.org/issues/29649 When I run `facter ipa` on an ipa enabled host I get no output: So when looking at the code:
if File.exist?('/etc/sssd/sssd.conf') && sssd = File.readlines('/etc/sssd/sssd.conf')
Jira (FACT-2588) ipa_facts : does not extract info from sssd.conf
Title: Message Title Ben Ford commented on FACT-2588 Re: ipa_facts : does not extract info from sssd.conf This appears to be a part of the joshuabaird/ipaclient module. Filing or contributing a pull request there will probably be your best bet at getting this fixed. Good luck! 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.357061.1588103651000.49288.1588104660026%40Atlassian.JIRA.
Jira (PUP-7197) make type aliases from modules available on the agent
Title: Message Title
Josh Cooper commented on PUP-7197
Re: make type aliases from modules available on the agent
Adding a new mount for sync'ing types isn't hard, but I think the way stdlib defines the types is a problem, since they end up as lib/types/httpurl.pp instead of lib/types/stdlib/httpurl.pp and the agent-side cache loader expects to find them in the latter, since they're specified as param 'Stdlib::HTTPUrl', :url in puppet code. If stdlib properly namespaced the types, like it does with deferred functions, e.g. lib/puppet/functions//myfunction.pp, then it wouldn't be hard to sync and load types on the agent. In $codedir/environments/production/module/mymodule/lib/puppet/functions/mymodule/myupcase.rb
Puppet::Functions.create_function(:'mymodule::myupcase') do
dispatch :from_url do
param 'Stdlib::HTTPUrl', :url
end
def from_url(url)
url
end
end
In $codedir/environments/production/module/mymodule/manifests/init.pp
class mymodule {
Jira (PUP-10451) Prepare release announcement (Puppet Platform 6.15.0)
Title: Message Title Nirupama Mantha commented on PUP-10451 Re: Prepare release announcement (Puppet Platform 6.15.0) The next release in the Puppet 6 series, Puppet 6.15.0, is now available! The release contains security and bug fixes and minor improvements, including: For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/latest/release_notes_puppet.html 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.356747.1587775913000.49729.1588119360032%40Atlassian.JIRA.
Jira (PUP-10461) Prepare release announcement (Puppet Platform 5.5.20)
Title: Message Title Nirupama Mantha commented on PUP-10461 Re: Prepare release announcement (Puppet Platform 5.5.20) The next point release in the Puppet 5.5 series, Puppet 5.5.20, is now available! The release contains security and bug fixes and minor improvements, including: For the full list of changes, check out the release notes: https://puppet.com/docs/puppet/5.5/release_notes.html 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.356780.1587776061000.49741.1588119480465%40Atlassian.JIRA.
Jira (PUP-10451) Prepare release announcement (Puppet Platform 6.15.0)
Title: Message Title Nirupama Mantha commented on PUP-10451 Re: Prepare release announcement (Puppet Platform 6.15.0) Nick Walker Margaret Lee 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.356747.1587775913000.49755.1588120740123%40Atlassian.JIRA.
Jira (PUP-10461) Prepare release announcement (Puppet Platform 5.5.20)
Title: Message Title Nirupama Mantha commented on PUP-10461 Re: Prepare release announcement (Puppet Platform 5.5.20) Nick Walker Margaret Lee 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.356780.1587776061000.49758.1588120800124%40Atlassian.JIRA.
Jira (PUP-10247) Support ruby 2.7
Title: Message Title Ed Marshall commented on PUP-10247 Re: Support ruby 2.7 FYI: Fedora 32 just shipped with ruby 2.7. 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.342962.1579675679000.49774.1588121100062%40Atlassian.JIRA.
Jira (FACT-2587) Puppet facts missing on facter 3.10.0 with OSP 6.13.0
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2587 Puppet facts missing on facter 3.10.0 with OSP 6.13.0 Change By: Mihai Buzgau Sprint: NW - 2020-05-13 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.357029.158809312.49830.1588140720034%40Atlassian.JIRA.
Jira (FACT-2589) Fix RSpec warnings
Title: Message Title
Gheorghe Popescu created an issue
Facter / FACT-2589
Fix RSpec warnings
Issue Type:
Task
Assignee:
Unassigned
Created:
2020/04/28 11:46 PM
Priority:
Normal
Reporter:
Gheorghe Popescu
There are some RSpec warnings that should be fixed
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect { }.not_to raise_error` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration._on_potential_false_positives_ = :nothing`. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/custom_facts/core/aggregate_spec.rb:41:in `block (3 levels) in '. [2020-04-29 09:43:22.564537 ] ERROR Facter - Failed to handle /tmp/foo.yaml as LegacyFacter::Util::Parser::YamlParser facts: no implicit conversion of nil into String [2020-04-29 09:43:22.566776 ] ERROR Facter - Failed to handle /tmp/foo.json as LegacyFacter::Util::Parser::JsonParser facts: no implicit conversion of nil into String WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect { }.not_to raise_error` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration._on_potential_false_positives_ = :nothing`. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/custom_fa
Jira (FACT-2589) Fix RSpec warnings
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2589
Fix RSpec warnings
Change By:
Gheorghe Popescu
{code:java} There are some RSpec warnings that should be fixed {noformat} WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect { }.not_to raise_error` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration._on_potential_false_positives_ = :nothing`. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/custom_facts/core/aggregate_spec.rb:41:in `block (3 levels) in '. [2020-04-29 09:43:22.564537 ] ERROR Facter - Failed to handle /tmp/foo.yaml as LegacyFacter::Util::Parser::YamlParser facts: no implicit conversion of nil into String [2020-04-29 09:43:22.566776 ] ERROR Facter - Failed to handle /tmp/foo.json as LegacyFacter::Util::Parser::JsonParser facts: no implicit conversion of nil into String WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect { }.not_to raise_error` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration._on_potential_false_positives_ = :nothing`. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/custom_facts/util/resolution_spec.rb:105:in `block (3 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/current_zone_resolver_spec.rb:9:in `block (2 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/zfs_resolver_spec.rb:6:in `block (2 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/zfs_resolver_spec.rb:6:in `block (2 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/zfs_resolver_spec.rb:6:in `block (2 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, us
Jira (FACT-2589) Fix RSpec warnings
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2589
Fix RSpec warnings
Change By:
Gheorghe Popescu
{code:java} There are some RSpec warnings that should be fixed WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect { }.not_to raise_error` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration._on_potential_false_positives_ = :nothing`. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/custom_facts/core/aggregate_spec.rb:41:in `block (3 levels) in '. [2020-04-29 09:43:22.564537 ] ERROR Facter - Failed to handle /tmp/foo.yaml as LegacyFacter::Util::Parser::YamlParser facts: no implicit conversion of nil into String [2020-04-29 09:43:22.566776 ] ERROR Facter - Failed to handle /tmp/foo.json as LegacyFacter::Util::Parser::JsonParser facts: no implicit conversion of nil into String WARNING StringWARNING : Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect { }.not_to raise_error` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration._on_potential_false_positives_ = :nothing`. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/custom_facts/util/resolution_spec.rb:105:in `block (3 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/current_zone_resolver_spec.rb:9:in `block (2 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/zfs_resolver_spec.rb:6:in `block (2 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/zfs_resolver_spec.rb:6:in `block (2 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/zfs_resolver_spec.rb:6:in `block (2 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effe
Jira (FACT-2589) Fix RSpec warnings
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2589
Fix RSpec warnings
Change By:
Gheorghe Popescu
{ code:java noformat } WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect { }.not_to raise_error` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration._on_potential_false_positives_ = :nothing`. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/custom_facts/core/aggregate_spec.rb:41:in `block (3 levels) in '. [2020-04-29 09:43:22.564537 ] ERROR Facter - Failed to handle /tmp/foo.yaml as LegacyFacter::Util::Parser::YamlParser facts: no implicit conversion of nil into String [2020-04-29 09:43:22.566776 ] ERROR Facter - Failed to handle /tmp/foo.json as LegacyFacter::Util::Parser::JsonParser facts: no implicit conversion of nil into StringWARNING StringWARNING : Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect { }.not_to raise_error` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration._on_potential_false_positives_ = :nothing`. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/custom_facts/util/resolution_spec.rb:105:in `block (3 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/current_zone_resolver_spec.rb:9:in `block (2 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/zfs_resolver_spec.rb:6:in `block (2 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/zfs_resolver_spec.rb:6:in `block (2 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/zfs_resolver_spec.rb:6:in `block (2 levels) in '. WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_val
Jira (FACT-2589) Fix RSpec warnings
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2589
Fix RSpec warnings
Change By:
Gheorghe Popescu
There are some warnings when running facter tests. You can reproduce this by running `bundle exec rspec spec` {noformat}WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect { }.not_to raise_error` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration._on_potential_false_positives_ = :nothing`. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/custom_facts/core/aggregate_spec.rb:41:in `block (3 levels) in '.[2020-04-29 09:43:22.564537 ] ERROR Facter - Failed to handle /tmp/foo.yaml as LegacyFacter::Util::Parser::YamlParser facts: no implicit conversion of nil into String[2020-04-29 09:43:22.566776 ] ERROR Facter - Failed to handle /tmp/foo.json as LegacyFacter::Util::Parser::JsonParser facts: no implicit conversion of nil into StringWARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect { }.not_to raise_error` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration._on_potential_false_positives_ = :nothing`. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/custom_facts/util/resolution_spec.rb:105:in `block (3 levels) in '.WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/current_zone_resolver_spec.rb:9:in `block (2 levels) in '.WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/zfs_resolver_spec.rb:6:in `block (2 levels) in '.WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/zfs_resolver_spec.rb:6:in `block (2 levels) in '.WARNING: `allow(...).to receive(..).ordered` is not supported and will have no effect, use `and_return(*ordered_values)` instead.. Called from /Users/gheorghe.popescu/Workspace/facter-ng/spec/facter/resolvers/solaris/zfs_resolver_spec.rb:6:in `block (2 levels) in '.WARNING: `allow(...).to receive(..).ordered` is no
Jira (FACT-2589) Fix RSpec warnings
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2589 Fix RSpec warnings Change By: Gheorghe Popescu Epic Link: FACT-2123 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.357116.1588142786000.49879.1588143540029%40Atlassian.JIRA.
