Jira (PUP-8729) Puppet does not accept UTF8 on the command line
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8729 Puppet does not accept UTF8 on the command line Change By: Josh Cooper Story Points: 3 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.128358.1461692616000.6008.1675128900024%40Atlassian.JIRA.
Jira (PUP-8729) Puppet does not accept UTF8 on the command line
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8729 Puppet does not accept UTF8 on the command line 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.128358.1461692616000.6007.1675128840026%40Atlassian.JIRA.
Jira (FACT-3155) Remove timecop from spec tests
Title: Message Title Josh Cooper updated an issue Facter / FACT-3155 Remove timecop from spec tests Change By: Josh Cooper Sprint: Phoenix 2023-02-15 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.470510.1665091007000.6003.1675126020030%40Atlassian.JIRA.
Jira (PDB-5581) Github PR pipeline doesn't report after acceptance test job
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5581 Github PR pipeline doesn't report after acceptance test job Change By: Austin Blatt Fix Version/s: PDB n/a 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.479496.1674513484000.5939.1675117800060%40Atlassian.JIRA.
Jira (PUP-11722) concurrent-ruby 1.2.0 breaks puppet
Title: Message Title
Romain Tartière updated an issue
Puppet / PUP-11722
concurrent-ruby 1.2.0 breaks puppet
Change By:
Romain Tartière
*Puppet Version: 7.x**Puppet Server Version: N/A**OS Name/Version: N/A*concurrent-ruby 1.2.0 was just released and breaks running Puppet using gem/bundler.It looks like puppet use a private class of this gem that got removed in:https://github.com/ruby-concurrency/concurrent-ruby/commit/30465396414e13290c3e1d8d26a0f2de2ebedc4c*Desired Behavior:*Puppet should work with concurrent-ruby 1.2.0*Actual Behavior:*{{romain@zappy ~/Projects/puppetlabs % git clone g...@github.com:puppetlabs/puppet.git}}{{romain@zappy ~/Projects/puppetlabs % cd puppet}}{{romain@zappy ~/Projects/puppetlabs/puppet % bundle install}}{{romain@zappy ~/Projects/puppetlabs/puppet % bundle show concurrent-ruby}}{{/usr/home/romain/.vendor/ruby/3.0/gems/concurrent-ruby-1.2.0}}{{romain@zappy ~/Projects/puppetlabs/puppet % bundle exec bin/puppet}}{{bundler: failed to load command: bin/puppet (bin/puppet)}}{{/usr/home/romain/Projects/puppetlabs/puppet/lib/puppet/thread_local.rb:6:in `': uninitialized constant Concurrent::RubyThreadLocalVar (NameError)}}{{Did you mean? Concurrent::RubyThreadPoolExecutor}}{{ from /usr/home/romain/Projects/puppetlabs/puppet/lib/puppet/context.rb:1:in `require_relative'}}{{ from /usr/home/romain/Projects/puppetlabs/puppet/lib/puppet/context.rb:1:in `'}}{{ from /usr/home/romain/Projects/puppetlabs/puppet/lib/puppet.rb:45:in `require_relative'}}{{ from /usr/home/romain/Projects/puppetlabs/puppet/lib/puppet.rb:45:in `'}}{{ from /usr/home/romain/Projects/puppetlabs/puppet/lib/puppet.rb:42:in `'}}{{ from /usr/home/romain/Projects/puppetlabs/puppet/lib/puppet/util/command_line.rb:12:in `require_relative'}}{{ from /usr/home/romain/Projects/puppetlabs/puppet/lib/puppet/util/command_line.rb:12:in `'}}{{ from bin/puppet:4:in `require'}}{{ from bin/puppet:4:in `'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/cli/exec.rb:58:in `load'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/cli/exec.rb:58:in `kernel_load'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/cli/exec.rb:23:in `run'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/cli.rb:483:in `exec'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/cli.rb:31:in `dispatch'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/cli.rb:25:in
Jira (PUP-11722) concurrent-ruby 1.2.0 breaks puppet
Title: Message Title
Romain Tartière updated an issue
Puppet / PUP-11722
concurrent-ruby 1.2.0 breaks puppet
Change By:
Romain Tartière
*Puppet Version: 7.x**Puppet Server Version: N/A**OS Name/Version: N/A*concurrent-ruby 1.2.0 was just released and breaks running Puppet using gem/bundler.It looks like puppet use a private class of this gem that got removed in:https://github.com/ruby-concurrency/concurrent-ruby/commit/30465396414e13290c3e1d8d26a0f2de2ebedc4c*Desired Behavior:*Puppet should work with concurrent-ruby 1.2.0*Actual Behavior:*{{ {} romain@zappy ~/Projects/puppetlabs % git clone g...@github.com:puppetlabs/puppet.git { }} } {{ {} romain@zappy ~/Projects/puppetlabs % cd puppet { }} } {{ {} romain@zappy ~/Projects/puppetlabs/puppet % bundle install { }} } {{ {} romain@zappy ~/Projects/puppetlabs/puppet % bundle show concurrent-ruby { }} } {{ {} /usr/home/romain/.vendor/ruby/3.0/gems/concurrent-ruby-1.2.0 { }} } {{ {} romain@zappy ~/Projects/puppetlabs/puppet % bundle exec bin/puppet { }} } {{bundler: failed to load command: bin/puppet (bin/puppet)}}{{/usr/home/romain/Projects/puppetlabs/puppet/lib/puppet/thread_local.rb:6:in `': uninitialized constant Concurrent::RubyThreadLocalVar (NameError)}}{{Did you mean? Concurrent::RubyThreadPoolExecutor}}{{ from /usr/home/romain/Projects/puppetlabs/puppet/lib/puppet/context.rb:1:in `require_relative'}}{{ from /usr/home/romain/Projects/puppetlabs/puppet/lib/puppet/context.rb:1:in `'}}{{ from /usr/home/romain/Projects/puppetlabs/puppet/lib/puppet.rb:45:in `require_relative'}}{{ from /usr/home/romain/Projects/puppetlabs/puppet/lib/puppet.rb:45:in `'}}{{ from /usr/home/romain/Projects/puppetlabs/puppet/lib/puppet.rb:42:in `'}}{{ from /usr/home/romain/Projects/puppetlabs/puppet/lib/puppet/util/command_line.rb:12:in `require_relative'}}{{ from /usr/home/romain/Projects/puppetlabs/puppet/lib/puppet/util/command_line.rb:12:in `'}}{{ from bin/puppet:4:in `require'}}{{ from bin/puppet:4:in `'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/cli/exec.rb:58:in `load'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/cli/exec.rb:58:in `kernel_load'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/cli/exec.rb:23:in `run'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/cli.rb:483:in `exec'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/cli.rb:31:in `dispatch'}}{{ from /usr/home/romain/.vendor/ruby/3.0/gems/bundler-2.3.12/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'}}{{ from
Jira (PDB-5560) Update PuppetDB terminus for Puppet 8/Ruby 3
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5560 Update PuppetDB terminus for Puppet 8/Ruby 3 Change By: Austin Blatt Assignee: Austin Blatt 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.474929.1668708016000.5888.1675108440029%40Atlassian.JIRA.
Jira (FACT-3178) Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-3178
Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC
Change By:
Josh Cooper
[puppet-team-phoenix-public|https://perforce.slack.com/archives/C049M3SC73M/p1673869007041499] A customer claims that on their Solaris server facter is failing to return expected results.12 replies For example:With Facter 4.2.5 (PE 2021.x), we face the following bug:Accessing fact ldom is OK: {noformat} (0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter ldom \ { domainchassis => "1249BDYDE1", domaincontrol => "oc-master-02-cd", domainname => "vdcf-mgmt-gd", domainrole => {control => "false",impl => "LDoms",io => "false",root => "false",service => "false" }, domainuuid => "edad1f61-ec07-efd1-f7da-fda1a9f35547"} {noformat} Accessing ldom.domainrole is also OK: {noformat} (0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter ldom.domainrole \ { control => "false", impl => "LDoms", io => "false", root => "false", service => "false"} {noformat} However, Accessing subitems of ldom.control do not work: {noformat} (0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter ldom.domainrole.impl(0)MGMT(gDom)root@vdcf-mgmt-gd:~# {noformat} However, when running the same command in debug mode, we see the value was successfully resolved to LDoms: {noformat} (130)MGMT(gDom)root@vdcf-mgmt-gd:~# facter ldom.domainrole.impl --debug[2023-01-11 18:38:00.437408 ] INFO Facter - executed with command line: ldom.domainrole.impl --debug [2023-01-11 18:38:00.437982 ] DEBUG Facter - Facter version: 4.2.5 [2023-01-11 18:38:00.442361 ] DEBUG Facter::FactManager - Resolving facts sequentially [2023-01-11 18:38:00.442909 ] DEBUG Facter::FactLoader - Loading all internal facts [2023-01-11 18:38:00.443405 ] DEBUG Facter::FactLoader - Loading custom facts [2023-01-11 18:38:00.447715 ] DEBUG Facter::FactLoader - Loading external facts [2023-01-11 18:38:00.448624 ] DEBUG LegacyFacter::Util::DirectoryLoader - Fact file /opt/puppetlabs/facter/facts.d/application.txt was parsed but no key=>value data was returned [2023-01-11 18:38:00.454139 ] DEBUG Facter::QueryParser - List of resolvable facts: [#] [2023-01-11 18:38:00.454412 ] DEBUG Facts::Solaris::Ldom - Solving the ldom fact. [2023-01-11 18:38:00.454613 ] DEBUG Facter::Core::Execution::Posix - Executing command: /usr/sbin/virtinfo -a -p [2023-01-11 18:38:00.500065 ] DEBUG Facter::FactManager - fact "ldom_domainrole_impl" has resolved to: LDoms [2023-01-11 18:38:00.500617 ] DEBUG Facter::LegacyFactFormatter - Formatting for single user query [2023-01-11 18:38:00.500997 ] DEBUG Facter::LegacyFactFormatter - Remove quotes from value if it is a simple string (0)MGMT(gDom)root@vdcf-mgmt-gd:~# {noformat} Facter version: {noformat} (0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter --version4.2.5 {noformat} Solaris version/architecture as follows: {noformat} (0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter os.release facter \ { full => "11.4", major => "11", minor => "4"}(0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter hardwareisa
Jira (FACT-3178) Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-3178
Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC
Change By:
Josh Cooper
[puppet-team-phoenix-public|https://perforce.slack.com/archives/C049M3SC73M/p1673869007041499] A Swisscom customer [50697|https://puppetlabs.zendesk.com/agent/tickets/50697] claims that on their Solaris server facter is failing to return expected results.12 repliesFor example:With Facter 4.2.5 (PE 2021.x), we face the following bug:Accessing fact ldom is OK:(0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter ldom\{ domainchassis => "1249BDYDE1", domaincontrol => "oc-master-02-cd", domainname => "vdcf-mgmt-gd", domainrole => {control => "false",impl => "LDoms",io => "false",root => "false",service => "false" }, domainuuid => "edad1f61-ec07-efd1-f7da-fda1a9f35547"}Accessing ldom.domainrole is also OK:(0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter ldom.domainrole\{ control => "false", impl => "LDoms", io => "false", root => "false", service => "false"} However, Accessing subitems of ldom.control do not work:(0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter ldom.domainrole.impl(0)MGMT(gDom)root@vdcf-mgmt-gd:~# However, when running the same command in debug mode, we see the value was successfully resolved to LDoms:(130)MGMT(gDom)root@vdcf-mgmt-gd:~# facter ldom.domainrole.impl --debug[2023-01-11 18:38:00.437408 ] INFO Facter - executed with command line: ldom.domainrole.impl --debug [2023-01-11 18:38:00.437982 ] DEBUG Facter - Facter version: 4.2.5 [2023-01-11 18:38:00.442361 ] DEBUG Facter::FactManager - Resolving facts sequentially [2023-01-11 18:38:00.442909 ] DEBUG Facter::FactLoader - Loading all internal facts [2023-01-11 18:38:00.443405 ] DEBUG Facter::FactLoader - Loading custom facts [2023-01-11 18:38:00.447715 ] DEBUG Facter::FactLoader - Loading external facts [2023-01-11 18:38:00.448624 ] DEBUG LegacyFacter::Util::DirectoryLoader - Fact file /opt/puppetlabs/facter/facts.d/application.txt was parsed but no key=>value data was returned [2023-01-11 18:38:00.454139 ] DEBUG Facter::QueryParser - List of resolvable facts: [#] [2023-01-11 18:38:00.454412 ] DEBUG Facts::Solaris::Ldom - Solving the ldom fact. [2023-01-11 18:38:00.454613 ] DEBUG Facter::Core::Execution::Posix - Executing command: /usr/sbin/virtinfo -a -p [2023-01-11 18:38:00.500065 ] DEBUG Facter::FactManager - fact "ldom_domainrole_impl" has resolved to: LDoms [2023-01-11 18:38:00.500617 ] DEBUG Facter::LegacyFactFormatter - Formatting for single user query [2023-01-11 18:38:00.500997 ] DEBUG Facter::LegacyFactFormatter - Remove quotes from value if it is a simple string (0)MGMT(gDom)root@vdcf-mgmt-gd:~# Facter version:(0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter --version4.2.5Solaris version/architecture as follows:(0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter os.releasefacter \{ full => "11.4", major => "11", minor => "4"}(0)MGMT(gDom)root@vdcf-mgmt-gd:~# facter hardwareisa sparc
Jira (FACT-3178) Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC
Title: Message Title Josh Cooper updated an issue Facter / FACT-3178 Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC Change By: Josh Cooper Epic Link: PUP-11658 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.479125.1673888594000.5793.1675096260029%40Atlassian.JIRA.
Jira (PUP-11685) Total number of fact warning not counting array elements
Title: Message Title Vadym Chepkov commented on PUP-11685 Re: Total number of fact warning not counting array elements FYI, puppet/systemd v4 exposes this flaw to all nodes 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.476077.1670253534000.5784.1675092420023%40Atlassian.JIRA.
Jira (PUP-4707) environment_timeout in puppet.conf not honored if environmentpath does not exist at startup
Title: Message Title Benjamin Rechsteiner commented on PUP-4707 Re: environment_timeout in puppet.conf not honored if environmentpath does not exist at startup Josh Cooper as i can see in puppet 7 environment_timeout and environment_ttl still not honored whether environmentpath is set or not. 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.83430.1433557323000.5761.1675084200024%40Atlassian.JIRA.
