Jira (PUP-8729) Puppet does not accept UTF8 on the command line
Title: Message Title Michael Hashizume assigned an issue to Michael Hashizume Puppet / PUP-8729 Puppet does not accept UTF8 on the command line Change By: Michael Hashizume Assignee: Michael Hashizume Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.128358.1461692616000.3554.1680812640026%40Atlassian.JIRA.
Jira (PUP-11814) loadbalancing documentation is unclear
Title: Message Title Tim Meusel commented on PUP-11814 Re: loadbalancing documentation is unclear Sorry, this was supposed to be a DOCUMENT ticket, could you please move it? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.483958.1680805807000.3527.1680805920020%40Atlassian.JIRA.
Jira (PUP-11814) loadbalancing documentation is unclear
Title: Message Title Tim Meusel created an issue Puppet / PUP-11814 loadbalancing documentation is unclear Issue Type: Task Assignee: Unassigned Created: 2023/04/06 11:30 AM Priority: Normal Reporter: Tim Meusel Hi, https://www.puppet.com/docs/pe/2021.7/installing_compilers.html#using-load-balancers-with-compilers-load_balancing_for_orchestration_scale is a bit unclear. Two quotes: > If you're not using HTTP health checks, we recommend using a round robin or random load balancing algorithm for PXP agent > Due to the diverse nature of the network communications between the agent and the primary server, we recommend that you implement a load balancing algorithm that distributes traffic between compilers based on the number of open connections. Load balancers often refer to this strategy as "balancing by least connections." Does that mean for pxp agents "round robin" is recommended" and for puppet agents "least connections"? Add Comment
Jira (FACT-3192) facter -p --no-external-facts is unusable
Title: Message Title Josh Cooper updated an issue Facter / FACT-3192 facter -p --no-external-facts is unusable Change By: Josh Cooper Summary: `` facter -p --no-external-facts `` causes ``ERROR Facter::OptionsValidator`` is unusable Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.483146.1679060554000.3516.1680804360030%40Atlassian.JIRA.
Jira (FACT-3192) ``facter -p --no-external-facts`` causes ``ERROR Facter::OptionsValidator``
Title: Message Title Josh Cooper updated an issue Facter / FACT-3192 ``facter -p --no-external-facts`` causes ``ERROR Facter::OptionsValidator`` Change By: Josh Cooper Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.483146.1679060554000.3511.1680804180096%40Atlassian.JIRA.
Jira (FACT-3192) ``facter -p --no-external-facts`` causes ``ERROR Facter::OptionsValidator``
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-3192
``facter -p --no-external-facts`` causes ``ERROR Facter::OptionsValidator``
Change By:
Josh Cooper
*Desired Behavior:*This command should work:{noformat}$ facter -p --no-external-facts{noformat}*Actual Behavior:*It fails because facter thinks both --external-facts and --no-external-facts have been specified:{noformat}[2023-04-06 10:59:58.501545 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one {noformat}*Description* A customer is seeing some unexpected behaviours when using facter as follows: * Using``{*}-p-{*}`` and ``{*}-no-external-facts{*}`` together produces an error ``{*}ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one{*}`` and no facts are returned * Other variations of facter options fail to return the expected custom factI have been able to replicate what the customer is seeing on my lab of {code}root@pe-server-238c28-1 development (development)$ facter --version4.2.14root@pe-server-238c28-1 development (development)$ {code} More detail of my lab setup: * I have a custom fact defined on my PE, e.g., my environment containse the custom fact here *site-modules/bigbird/lib/facter/bigbird.rb* * I can see my ``bigbird`` custom fact as expected: {code}root@pe-server-238c28-1 pe_curl_requests (development)$ facter -p bigbird{ role => "role::replica", sshkey => { identifier => "pe-server-238c28-1.us-west1-b.c.customer-support-scratchpad.internal", key => "LONGLONGLONGPUBLICKEY", type => "ssh-rsa" }}root@pe-server-238c28-1 pe_curl_requests (development)$ facter -p | grep bigbirdbigbird => {root@pe-server-238c28-1 pe_curl_requests (development)$ {code} * However, when I introduce other flags I see expected results: {code}# these workroot@pe-server-238c28-1 development (development)$ facter -p --json | grep -E "(oslogin|[^/]bigbird)" "bigbird": { "oslogin": {root@pe-server-238c28-1 development (development)$ facter -p bigbird --json | grep -E "(oslogin|[^/]bigbird)" "bigbird": {root@pe-server-238c28-1 development (development)$ # these don't work# custom fact 'bigbird' is not returned unexpectedlyroot@pe-server-238c28-1 development (development)$ facter --json | grep -E "(oslogin|[^/]bigbird)" "oslogin": {root@pe-server-238c28-1 development (development)$ # no facts returned AND an error is thrownroot@pe-server-238c28-1 development (development)$ facter -p --no-external-facts | grep -E "(oslogin|[^/]bigbird)"[2023-03-17 13:28:08.334765 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one root@pe-server-238c28-1 development (development)$ facter -p --no-external-facts --json | grep -E "(oslogin|[^/]bigbird)"[2023-03-17 13:28:15.077332 ] ERROR Facter::OptionsValidator - no-external-facts and external-dir options conflict: please specify only one root@pe-server-238c28-1 development (development)$ facter -p bigbird --no-external-f
Jira (FACT-2772) Facter 4 fails to guard against recursion (FACT-1373)
Title: Message Title Josh Cooper updated an issue Facter / FACT-2772 Facter 4 fails to guard against recursion (FACT-1373) Change By: Josh Cooper Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.370195.1598387754000.3509.1680803940026%40Atlassian.JIRA.
Jira (FACT-2772) Facter 4 fails to guard against recursion (FACT-1373)
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-2772
Facter 4 fails to guard against recursion (FACT-1373)
Change By:
Josh Cooper
After updating puppet to verision 6.18.0-1, the following script, located in `/opt/puppetlabs/facter/facts.d/` recurses into oblivion {noformat}#!/usr/bin/env rubyrequire 'json'osfamily = %x(/opt/puppetlabs/bin/facter --no-custom-facts --no-external-facts os.family).strip@data = ""> packages: {}}def parse_redhat packagelist = %x(rpm -qa --qf '%{NAME};%{VERSION}-%{RELEASE}\n').split("\n") packagelist.each do |package|pname = package.split(';').firstversion = package.split(';').last@data[:packages][pname] = version.strip endenddef parse_debian packagelist = %x(dpkg-query -W -f='${binary:Package};${Version}\n').split("\n") packagelist.each do |package|pname = package.split(';').firstversion = package.split(';').last@data[:packages][pname] = version.strip endendif osfamily == 'RedHat' parse_redhatendif osfamily == 'Debian' parse_debianendputs @data.to_json{noformat} I created this ticket after I talked to the slack community puppet guy Josh ([https://puppetcommunity.slack.com/archives/C0W298S9G/p1598386635326500)]{quote}"@kervyn facter 3.x (which is the default in puppet 6) has logic to prevent external facts from calling facter recursively (FACT-1373) but it seems that's not working as expected. Can you file a FACT ticket and link the 1373?"{quote}For this ticket, Facter 4 should check if the INSIDE_FACTER environment variable is set prior to evaluating external facts.If it's not set, then set the variable, see how this is implemented in facter 3 https://github.com/puppetlabs/facter/blob/6d7ffc6efdfbc3b1fc79311cdeb4581ac2098d9c/exe/facter.cc#L282-L293If recursion is detected, facter should emit an error similar to "Facter was called recursively, skipping external facts. Add '--no-external-facts' to silence this warning" and it should automatically ignore external facts. You may want to implement this in {{lib/facter/framework/cli/cli.rb}} Need to account for different ways facter can be called (via command line, puppet, to_hash, resolve(''), resolve('os.family')). Create additional tickets as needed.
Add Comment
Jira (FACT-2772) Facter 4 fails to guard against recursion (FACT-1373)
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-2772
Facter 4 fails to guard against recursion (FACT-1373)
Change By:
Josh Cooper
After updating puppet to verision 6.18.0-1, the following script, located in `/opt/puppetlabs/facter/facts.d/` recurses into oblivion {noformat}#!/usr/bin/env rubyrequire 'json'osfamily = %x(/opt/puppetlabs/bin/facter --no-custom-facts --no-external-facts os.family).strip@data = ""> packages: {}}def parse_redhat packagelist = %x(rpm -qa --qf '%{NAME};%{VERSION}-%{RELEASE}\n').split("\n") packagelist.each do |package|pname = package.split(';').firstversion = package.split(';').last@data[:packages][pname] = version.strip endenddef parse_debian packagelist = %x(dpkg-query -W -f='${binary:Package};${Version}\n').split("\n") packagelist.each do |package|pname = package.split(';').firstversion = package.split(';').last@data[:packages][pname] = version.strip endendif osfamily == 'RedHat' parse_redhatendif osfamily == 'Debian' parse_debianendputs @data.to_json{noformat} I created this ticket after I talked to the slack community puppet guy Josh ([https://puppetcommunity.slack.com/archives/C0W298S9G/p1598386635326500)]{quote}"@kervyn facter 3.x (which is the default in puppet 6) has logic to prevent external facts from calling facter recursively (FACT-1373) but it seems that's not working as expected. Can you file a FACT ticket and link the 1373?"{quote}For this ticket, Facter 4 should check if the INSIDE_FACTER environment variable is set prior to evaluating external facts. If it's not set, then set the variable . See , see how this is implemented in facter 3 https://github.com/puppetlabs/facter/blob/6d7ffc6efdfbc3b1fc79311cdeb4581ac2098d9c/exe/facter.cc#L282-L293 If recursion is detected, facter would should emit an error similar to "Facter was called recursively, skipping external facts. Add '--no-external-facts' to silence this warning" and it should automatically ignore external facts. You may want to implement this in {{lib/facter/framework/cli/cli.rb}}
Add Comment
Jira (FACT-2772) Facter 4 fails to guard against recursion (FACT-1373)
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-2772
Facter 4 fails to guard against recursion (FACT-1373)
Change By:
Josh Cooper
After updating puppet to verision 6.18.0-1, the following script, located in `/opt/puppetlabs/facter/facts.d/` recurses into oblivion {noformat}#!/usr/bin/env rubyrequire 'json'osfamily = %x(/opt/puppetlabs/bin/facter --no-custom-facts --no-external-facts os.family).strip@data = ""> packages: {}}def parse_redhat packagelist = %x(rpm -qa --qf '%{NAME};%{VERSION}-%{RELEASE}\n').split("\n") packagelist.each do |package|pname = package.split(';').firstversion = package.split(';').last@data[:packages][pname] = version.strip endenddef parse_debian packagelist = %x(dpkg-query -W -f='${binary:Package};${Version}\n').split("\n") packagelist.each do |package|pname = package.split(';').firstversion = package.split(';').last@data[:packages][pname] = version.strip endendif osfamily == 'RedHat' parse_redhatendif osfamily == 'Debian' parse_debianendputs @data.to_json{noformat} I created this ticket after I talked to the slack community puppet guy Josh ([https://puppetcommunity.slack.com/archives/C0W298S9G/p1598386635326500)]{quote}"@kervyn facter 3.x (which is the default in puppet 6) has logic to prevent external facts from calling facter recursively (FACT-1373) but it seems that's not working as expected. Can you file a FACT ticket and link the 1373?"{quote} For this ticket, Facter 4 should check if the INSIDE_FACTER environment variable is set prior to evaluating external facts. If it's not set, then set the variable. See how this is implemented in facter 3 https://github.com/puppetlabs/facter/blob/6d7ffc6efdfbc3b1fc79311cdeb4581ac2098d9c/exe/facter.cc#L282-L293 If recursion is detected, facter would emit an error similar to "Facter was called recursively, skipping external facts. Add '--no-external-facts' to silence this warning" and it should automatically ignore external facts.
Add Comment
Jira (FACT-3151) Facter fails on the `/etc/os-release` that contains the '#`
Title: Message Title Josh Cooper updated an issue Facter / FACT-3151 Facter fails on the `/etc/os-release` that contains the '#` Change By: Josh Cooper Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.469451.1664227327000.3505.1680803160021%40Atlassian.JIRA.
Jira (PUP-10928) Add a setting to prevent falling back to non-rich data
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10928 Add a setting to prevent falling back to non-rich data Change By: Josh Cooper Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.388074.1613713885000.3504.1680803040029%40Atlassian.JIRA.
Jira (PUP-11813) Parenthesized expression causes EPP template validation failures
Title: Message Title
Torbjörn Lönnemark created an issue
Puppet / PUP-11813
Parenthesized _expression_ causes EPP template validation failures
Issue Type:
Bug
Assignee:
Unassigned
Created:
2023/04/06 10:36 AM
Priority:
Normal
Reporter:
Torbjörn Lönnemark
Puppet Version: 7.23.0 The following EPP template:
# any content
<% ([1, 2, 3] + [7, 8, 9]).each |$x| { -%>
<%= $x %>
<% } -%>
fails validation with:
$ puppet epp validate test.pp
Jira (PUP-11785) Don't fallback if catalog rendering fails
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11785 Don't fallback if catalog rendering fails Change By: Josh Cooper If puppetserver fails to serialize a catalog to JSON it will fallback to PSON, because there was a time where rich data wasn't supported end-to-end between server and agents. However, rich data is now enabled by default and supported end-to-end. And it required when using Deferred or Sensitive parameters. Therefore, if puppetserver downgrades to PSON it can lead to surprising behavior as described in PUP-10928.In Puppet 8, we will no longer fallback if catalog rendering/serialization fails. A new puppet setting will be added to 7.x in PUP-10928. For this ticket, the default value should be changed to not fallback and to raise an exception failing compilation (even if the puppet-pson gem has been installed). Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" gr
Jira (PUP-11786) Update jenkins runners to use ruby 3.1
Title: Message Title Josh Cooper commented on PUP-11786 Re: Update jenkins runners to use ruby 3.1 Released beaker 4.40 which allows beaker 4 to run on Ruby 3.1 Next up, update bundler gem used in ruby 3.1.1 on static jenkins hosts. Then update core modules to run with ruby 3.1.1 (and test with beaker 4.40 & puppet 8) Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.483500.1679604378000.3478.1680797400039%40Atlassian.JIRA.
Jira (PUP-11786) Update jenkins runners to use ruby 3.1
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-11786 Update jenkins runners to use ruby 3.1 Change By: Josh Cooper Assignee: Michael Hashizume Josh Cooper Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.483500.1679604378000.3479.1680797400100%40Atlassian.JIRA.
Jira (PUP-10928) Add a setting to prevent falling back to non-rich data
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10928 Add a setting to prevent falling back to non-rich data Change By: Josh Cooper Fix Version/s: PUP 7.25.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.388074.1613713885000.3475.1680796560020%40Atlassian.JIRA.
Jira (FACT-2954) Improve fact blocking mechanism in Facter 4
Title: Message Title Josh Cooper assigned an issue to Unassigned Facter / FACT-2954 Improve fact blocking mechanism in Facter 4 Change By: Josh Cooper Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.389707.1614771236000.3474.1680796380020%40Atlassian.JIRA.
Jira (FACT-3000) Dot notation implemented in Facter 4 is incomplete
Title: Message Title Josh Cooper updated an issue Facter / FACT-3000 Dot notation implemented in Facter 4 is incomplete Change By: Josh Cooper Flagged: Impediment Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.393010.1616788653000.3473.1680796320021%40Atlassian.JIRA.
