Jira (PUP-10723) Shadow fact / plan variable collisions in PAL catalog compiler
Title: Message Title Tom Beech updated an issue Puppet / PUP-10723 Shadow fact / plan variable collisions in PAL catalog compiler Shadow fact/variable collisions in PAL catalog compiler. Change By: Tom Beech Release Notes: Bug Fix Release Notes Summary: Shadow fact/variable collisions in PAL catalog compiler. 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
Jira (PUP-10850) Puppet facts show doesn't have an opt out option for legacy facts
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10850 Puppet facts show doesn't have an opt out option for legacy facts Change By: Josh Cooper Release Notes Summary: By default, 'puppet facts show' application displays all facts, including legacy facts. A new option, --no-legacy, was added to disable legacy facts when querying for all facts. The --show-legacy facts option remains, but is ignored, as that is the default behavior. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.382858.1610379246000.116795.1610751600077%40Atlassian.JIRA.
Jira (PUP-10850) Puppet facts show doesn't have an option to opt out of legacy facts
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10850 Puppet facts show doesn't have an option to opt out of legacy facts Change By: Josh Cooper Summary: Puppet facts show doesn't have an option to opt out option for of legacy facts Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.382858.1610379246000.116796.1610751600374%40Atlassian.JIRA.
Jira (PUP-10850) Puppet facts show doesn't have an opt out option for legacy facts
Title: Message Title Josh Cooper commented on PUP-10850 Re: Puppet facts show doesn't have an opt out option for legacy facts Merged to main in https://github.com/puppetlabs/puppet/commit/309d69a16265f9d0672fd7c654bbfab6931998db and a follow up commit to restore the --show-legacy argument was added in https://github.com/puppetlabs/puppet/commit/a600c40f32cfbcf77d58ae19f62ff5710a7fe940 Passed CI in 95ee12262 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.382858.1610379246000.116794.1610751540127%40Atlassian.JIRA.
Jira (PUP-10818) Cached catalog contains the result of deferred evaluation instead of the deferred function
Title: Message Title Josh Cooper commented on PUP-10818 Re: Cached catalog contains the result of deferred evaluation instead of the deferred function Merged to 6.x in https://github.com/puppetlabs/puppet/commit/c19368514167926332ba6cc5445fea43016b6ce3 and https://github.com/puppetlabs/puppet/commit/376d0aa36235f9401e82655280308d46adca2b48 Passed CI in 95ee1226 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.380551.1607542151000.116791.1610751300069%40Atlassian.JIRA.
Jira (PUP-10851) Error "Entry 'allow *' is unsupported and will be ignored" shown during PE upgrade
Title: Message Title Josh Cooper commented on PUP-10851 Re: Error "Entry 'allow *' is unsupported and will be ignored" shown during PE upgrade Merged to main in https://github.com/puppetlabs/puppet/commit/593f3c8d57036ce14c4e6155c5040651fc106430 Passed CI in puppet#95ee122621 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.383035.1610493103000.116789.1610751240464%40Atlassian.JIRA.
Jira (PUP-10842) Issue with puppet creating production folder when multiple environment paths are set
Title: Message Title Josh Cooper commented on PUP-10842 Re: Issue with puppet creating production folder when multiple environment paths are set Passed CI in puppet#95ee122621 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.381531.1608552353000.116775.1610751120030%40Atlassian.JIRA.
Jira (PUP-10819) 3x functions cannot be called from deferred functions in puppet agent
Title: Message Title Josh Cooper commented on PUP-10819 Re: 3x functions cannot be called from deferred functions in puppet agent Passed CI in puppet#95ee122621 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.380575.1607560522000.116776.1610751120076%40Atlassian.JIRA.
Jira (PUP-9176) puppet module install should list unsatisfiable dependencies if installation fails
Title: Message Title Josh Cooper commented on PUP-9176 Re: puppet module install should list unsatisfiable dependencies if installation fails Passed CI in puppet#95ee122621 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.51451.1410900284000.116774.1610751060037%40Atlassian.JIRA.
Jira (PUP-10856) Slower puppet agent run after agent upgrade to version 6
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10856 Slower puppet agent run after agent upgrade to version 6 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.383327.1610697413000.116552.1610740140119%40Atlassian.JIRA.
Jira (PUP-10855) Need to inject loaders when retrieving a catalog via Puppet::Resource::Catalog
Title: Message Title Josh Cooper commented on PUP-10855 Re: Need to inject loaders when retrieving a catalog via Puppet::Resource::Catalog This behavior is expected. In puppet 6, agents default to requesting a so called "rich data" catalog, which allows puppet to serialize data types that aren't natively supported in JSON, such as sensitive, binary, deferred, etc. Note the Accept: application/vnd.puppet.rich+json, ... header: bx puppet agent -t --http_debug > /dev/null 2>&1 | grep -e 'puppet/v3/catalog' <- "POST /puppet/v3/catalog/localhost?environment=production HTTP/1.1\r\nX-Puppet-Version: 6.20.0\r\nUser-Agent: Puppet/6.20.0 Ruby/2.5.8-p224 (x86_64-darwin18)\r\nAccept: application/vnd.puppet.rich+json, application/json, application/vnd.puppet.rich+msgpack, application/x-msgpack, text/pson\r\nContent-Type: application/x-www-form-urlencoded\r\nAccept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3\r\nHost: silly-devotion.delivery.puppetlabs.net:8140\r\nContent-Length: 24765\r\n\r\n" Depending on what your application needs to do, you could instead ask for a "json" catalog, for example if you're doing a plain diff of the catalog. bx puppet agent -t --http_debug --no-rich_data > /dev/null 2>&1 | grep -e 'puppet/v3/catalog' <- "POST /puppet/v3/catalog/localhost?environment=production HTTP/1.1\r\nX-Puppet-Version: 6.20.0\r\nUser-Agent: Puppet/6.20.0 Ruby/2.5.8-p224 (x86_64-darwin18)\r\nAccept: application/json, application/x-msgpack, text/pson\r\nContent-Type: application/x-www-form-urlencoded\r\nAccept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3\r\nHost: silly-devotion.delivery.puppetlabs.net:8140\r\nContent-Length: 24765\r\n\r\n" If you need to preserve the puppet data types, then you will need to setup the loaders in the client application. Note in puppet 7 (and in later versions of puppet 6.x), it's not necessary to use the indirector to retrieve catalogs from the server. You might want to take a look at the new http client, something like:
Jira (PUP-10776) Update Public-facing Puppet docs to include Ubuntu 20.04 aarch
Title: Message Title Mihai Buzgau commented on PUP-10776 Re: Update Public-facing Puppet docs to include Ubuntu 20.04 aarch Claire Cadman we're adding Ubuntu 20.04 AARCH in the Puppet Agent 6.20.0. Can you please help us by adding it to our public docs. Thank you! 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.377572.1604932238000.116457.1610736000119%40Atlassian.JIRA.
Jira (PUP-10856) Slower puppet agent run after agent upgrade to version 6
Title: Message Title Josh Cooper moved an issue Puppet / PUP-10856 Slower puppet agent run after agent upgrade to version 6 Change By: Josh Cooper Component/s: puppet-runtime Key: PA PUP - 3542 10856 Affects Version/s: puppet-agent 6.19.0 Project: Puppet Agent Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (PUP-10856) Slower puppet agent run after agent upgrade to version 6
Title: Message Title Josh Cooper commented on PUP-10856 Re: Slower puppet agent run after agent upgrade to version 6 Thanks Ashok Mahajan. I moved this to the PUP project. We'll take a look. 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.383327.1610697413000.116442.1610735640247%40Atlassian.JIRA.
Jira (PUP-10856) Slower puppet agent run after agent upgrade to version 6
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10856 Slower puppet agent run after agent upgrade to version 6 Change By: Josh Cooper Affects Version/s: PUP 6.19.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.383327.1610697413000.116441.1610735640203%40Atlassian.JIRA.
Jira (FACT-2922) Add --timing to puppet facts show
Title: Message Title Tom Parker created an issue Facter / FACT-2922 Add --timing to puppet facts show Issue Type: Improvement Assignee: Unassigned Created: 2021/01/15 10:28 AM Priority: Normal Reporter: Tom Parker facter --timing is incredibly useful to find slow facts on my systems however with the removal of the --puppet flag it only shows the built in facts. Would it be possible to have the --timing flag added to the puppet facts show command to show slow puppet fact resolutions as well? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-3715) PuppetDB doesn't complete shutdown after migration fails
Title: Message Title Rob Browning commented on PDB-3715 Re: PuppetDB doesn't complete shutdown after migration fails I suspect/hope we may have fixed this – just need to re-test when someone has a bit of time. 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.216460.1508186567000.116260.161073165%40Atlassian.JIRA.
Jira (PDB-231) Add Postgres disk space full warnings
Title: Message Title Rob Browning commented on PDB-231 Re: Add Postgres disk space full warnings I feel like the broader issue here is one that should be handled more systemically, i.e. puppetdb, puppetserver, the console, etc. perhaps shouldn't each be in charge of making sure systems have sufficient disk space and reporting it. There should be some broader system/host-level monitoring to handle that. So I'm going to close this for now, but feel free to re-open it and/or reassign it if you feel like that's not convincing. 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.21123.1386951055000.116238.1610728740101%40Atlassian.JIRA.
Jira (FACT-2921) LinuxMint Tessa not recognized, destroys services
Title: Message Title Hanno Steinke updated an issue Facter / FACT-2921 LinuxMint Tessa not recognized, destroys services Change By: Hanno Steinke Environment: root@bravo:~# cat /etc/os-release NAME=" Linux Mint "VERSION=" 19.1 ( Tessa )"ID=linuxmintID_LIKE=ubuntuPRETTY_NAME="Linux Mint 19.1"VERSION_ID="19.1"HOME_URL="https://www.linuxmint.com/"SUPPORT_URL="https://forums.linuxmint.com/"BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"PRIVACY_POLICY_URL="https://www.linuxmint.com/"VERSION_CODENAME=tessaUBUNTU_CODENAME=bionic root@bravo:~# lsb_release -aNo LSB modules are available.Distributor ID: LinuxMintDescription: Linux Mint 19.1 TessaRelease: 19.1Codename: tessa 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.383388.1610724788000.116178.1610725440030%40Atlassian.JIRA.
Jira (FACT-2921) LinuxMint Tessa not recognized, destroys services
Title: Message Title Hanno Steinke commented on FACT-2921 Re: LinuxMint Tessa not recognized, destroys services To help clarify this, here are the OS details: root@bravo:~# lsb_release -a No LSB modules are available. Distributor ID: LinuxMint Description: Linux Mint 19.1 Tessa Release: 19.1 Codename: tessa root@bravo:~# cat /etc/debian_version buster/sid root@bravo:~# cat /etc/os-release NAME="Linux Mint" VERSION="19.1 (Tessa)" ID=linuxmint ID_LIKE=ubuntu PRETTY_NAME="Linux Mint 19.1" VERSION_ID="19.1" HOME_URL="https://www.linuxmint.com/" SUPPORT_URL="https://forums.linuxmint.com/" BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/" PRIVACY_POLICY_URL="https://www.linuxmint.com/" VERSION_CODENAME=tessa UBUNTU_CODENAME=bionic 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.383388.1610724788000.116177.1610725380024%40Atlassian.JIRA.
Jira (FACT-2921) LinuxMint Tessa not recognized, destroys services
Title: Message Title
Hanno Steinke created an issue
Facter / FACT-2921
LinuxMint Tessa not recognized, destroys services
Issue Type:
Bug
Affects Versions:
FACT 4.0.47
Assignee:
Unassigned
Components:
Facter 4
Created:
2021/01/15 7:33 AM
Environment:
root@bravo:~# cat /etc/os-release NAME="Linux Mint" VERSION="19.1 (Tessa)" ID=linuxmint ID_LIKE=ubuntu PRETTY_NAME="Linux Mint 19.1" VERSION_ID="19.1" HOME_URL="https://www.linuxmint.com/" SUPPORT_URL="https://forums.linuxmint.com/" BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/" PRIVACY_POLICY_URL="https://www.linuxmint.com/" VERSION_CODENAME=tessa UBUNTU_CODENAME=bionic root@bravo:~# lsb_release -a No LSB modules are available. Distributor ID: LinuxMint Description: Linux Mint 19.1 Tessa Release: 19.1 Codename: tessa
Priority:
Normal
Reporter:
Hanno Steinke
After upgrading puppet to puppet 7 on LinuxMint 19.1 Tessa, all services deployed by Puppet were broken because they have been considered as upstart instead of systemd. Downgrading to puppet 6 corrected the issue. I did not completely understand the logic, but it seems to be caused by these different facter outputs: {{ root@bravo:~# facter --version 4.0.47 root@bravo:~# facter os { architecture => "amd64", distro => { codename => "tessa", description => "Linux Mint 19.1", id => "Linuxmint", release => { full => "19.1", major => "19.1" } }, family => "Ubuntu", hardware => "x86_64", name => "Linux", release => { full => "19.1", major => "19.1" } , selinux => { enabled => false } } root@bravo:~# facter --version 3.14.14
Jira (PUP-10815) Implement a puppet facts action that show fact differences between facter 3 and facter 4
Title: Message Title Claire Cadman updated an issue Puppet / PUP-10815 Implement a puppet facts action that show fact differences between facter 3 and facter 4 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.380233.1607442379000.116094.1610719920026%40Atlassian.JIRA.
Jira (PUP-10815) Implement a facts action that show fact differences between facter 3 and facter 4
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10815 Implement a facts action that show fact differences between facter 3 and facter 4 Change By: Gheorghe Popescu Summary: When upgrading to Puppet 7, the Puppet-Agent module should check if there are diffs Implement a facts action that show fact differences between facters facter 3 and facter 4 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.380233.1607442379000.116086.1610718720147%40Atlassian.JIRA.
Jira (PUP-10815) Implement a puppet facts action that show fact differences between facter 3 and facter 4
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10815 Implement a puppet facts action that show fact differences between facter 3 and facter 4 Change By: Gheorghe Popescu Summary: Implement a puppet facts action that show fact differences between facter 3 and facter 4 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.380233.1607442379000.116087.1610718720191%40Atlassian.JIRA.
Jira (PUP-10815) When upgrading to Puppet 7, the Puppet-Agent module should check if there are diffs between facters
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10815 When upgrading to Puppet 7, the Puppet-Agent module should check if there are diffs between facters Change By: Gheorghe Popescu Fix Version/s: PUP 6.20.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.380233.1607442379000.116083.1610718600026%40Atlassian.JIRA.
Jira (FACT-2919) Aggregate facts are broken
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Facter / FACT-2919 Aggregate facts are broken Change By: Gheorghe Popescu Assignee: Gheorghe Popescu 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.383308.1610670203000.116082.1610718540027%40Atlassian.JIRA.
Jira (FACT-2920) Random failing unit tests
Title: Message Title
Andrei Filipovici created an issue
Facter / FACT-2920
Random failing unit tests
Issue Type:
Task
Assignee:
Unassigned
Created:
2021/01/15 5:47 AM
Priority:
Normal
Reporter:
Andrei Filipovici
Kenyon pointed out in PR https://github.com/puppetlabs/facter/pull/2241 that some unit tests fail because of improper stubs. I added unit tests. Everything passes locally for me, except for random unit test failures unrelated to my changes, where the test returns facts from my system instead of from fixtures; spec_integration/facter_to_hash_spec.rb tests that return statvfs() function failed: Permission denied, I guess because I'm not running these tests as root. Example of the random failures: 1) Facter::Resolvers::OsRelease when on Oracle Linux returns os NAME Failure/Error: expect(result).to eq('OracleLinux') expected: "OracleLinux" got: "Debian" (compared using ==)
./spec/facter/resolvers/os_release_spec.rb:118:in `block (3 levels) in '
Add Comment
Jira (FACT-2919) Aggregate facts are broken
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2919 Aggregate facts are broken Change By: Gheorghe Popescu Release Notes: Bug Fix Release Notes Summary: Fixed a bug where facter was breaking when trying to add a debug message for the location where an aggregate facts is resolved from. This only happed for aggregate facts that return an array or hash, without having an aggregate block call. 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.383308.1610670203000.116080.1610717760033%40Atlassian.JIRA.
Jira (PUP-10842) Issue with puppet creating production folder when multiple environment paths are set
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10842 Issue with puppet creating production folder when multiple environment paths are set Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: The `production` environment folder used to be automatically created, at every Puppet run, in the first search path (given in the 'environmentpath' setting) if it did not already exist there. This fix makes sure to search through all the given paths before creating any new `production` environment folder. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.381531.1608552353000.116070.1610715480041%40Atlassian.JIRA.
Jira (FACT-2919) Aggregate facts are broken
Title: Message Title Gheorghe Popescu commented on FACT-2919 Re: Aggregate facts are broken https://github.com/puppetlabs/facter/pull/2257 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.383308.1610670203000.116008.1610706060029%40Atlassian.JIRA.
Jira (PUP-10855) Need to inject loaders when retrieving a catalog via Puppet::Resource::Catalog
Title: Message Title Nacho Barrientos created an issue Puppet / PUP-10855 Need to inject loaders when retrieving a catalog via Puppet::Resource::Catalog Issue Type: Bug Assignee: Unassigned Created: 2021/01/15 1:45 AM Priority: Normal Reporter: Nacho Barrientos Puppet Version: 6.15.0 Puppet Server Version: Does not apply OS Name/Version: CentOS8 Hi, Opening this for discussion mainly, it might not be a bug. We have an in-house debugging tool that downloads a catalog from a master and persists it to disk (serialised as JSON) to further inspection later on by another tool. Inspired by this, the code is something like this: require 'puppet' require 'puppet/face' Puppet.initialize_settings Puppet.initialize_facts Puppet.settings.preferred_run_mode = :agent
