Jira (PUP-11718) Delete ruby < 3.1 specific code paths
Title: Message Title Michael Hashizume assigned an issue to Michael Hashizume Puppet / PUP-11718 Delete ruby < 3.1 specific code paths 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.479201.1673977006000.4520.1681253280089%40Atlassian.JIRA.
Jira (PDB-5611) Remove legacy fact usage from PuppetDB module
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5611 Remove legacy fact usage from PuppetDB module 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.482931.1678895661000.4505.1681251060247%40Atlassian.JIRA.
Jira (PUP-11348) Remove Windows ENV patches on Ruby 3
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-11348
Remove Windows ENV patches on Ruby 3
Change By:
Josh Cooper
Ruby on Windows now stores environment variables and values as UTF-8, see [https://bugs.ruby-lang.org/issues/9715#note-8] so we should be able to remove .Using the various monkey patches and workarounds in latest puppet -agent and runtime with the default external encoding set to "locale" , such as modify {{ Puppet::Util. get_env}} Puppet should be able to: * manage registry entries with non-ascii characters * manage users with umlat , C:\Users\Jöhn * execute process with non-ascii in {{clear_environment}} and {{set_env}} to no longer special case Windows and just delegate to Ruby's {{ENV}}. Then try to reproduce the command line as a non-ascii user * get/set environment variables with rune characters: [ issue described in https://bugs.ruby-lang.org/ issues projects / 8822#note ruby - 6]See related info in :https: master / /tickets.puppetlabs.com/browse/PUP-5726 activity ? focusedCommentId from = 261201&page=com.atlassian.jira.plugin.system.issuetabpanels:comment 2016 - tabpanel#comment 06 - 261201https://tickets.puppetlabs.com/browse/PUP-5768?focusedCommentId=273221 22 to see that environment values can be set & page=com get correctly . atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-273221 And Environment names should be case insensitive. {code:puppet} exec { 'tomcat-configure-service': command => "powershell Environment values should be case preserving . exe Get-ChildItem Env:", onlyif => 'powershell It should be possible to get/set environment values using characters that are valid for the current locale, e . exe exit 0' g. if chcp is set to CP1252 , provider => windows, it should be possible to store extended ascii characters as values like Á logoutput => true, #notify => $tomcat_service Also related , tag => 'tomcat-configure-service' if the current user profile contains extended ascii , then it should be possible to do: } { code}{ noformat}set USERNAME=Jöhnset USERPROFILE=C:\Users\JöhnC:\> puppet apply manifests\bug_swedish_userprofile.pp --test{noformat} See more details in: https://tickets.puppetlabs.com/browse/PUP-5726?focusedCommentId=261201&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-261201
Jira (PUP-11813) Parenthesized expression causes EPP template validation failures
Title: Message Title
Josh Cooper commented on PUP-11813
Re: Parenthesized _expression_ causes EPP template validation failures
Torbjörn Lönnemark thanks for letting us know. Note the leading comment is causing validation to fail. If you remove # any content then epp validation succeeds:
~/work/puppet 7.x*
❯ cat epp.pp
<% ([1, 2, 3] + [7, 8, 9]).each |$x| { -%>
<%= $x %>
<% } -%>
~/work/puppet 7.x*
❯ bx puppet epp validate epp.pp
~/work/puppet 7.x*
❯ echo $?
0
Similary, if you remove the comment from:
Jira (PUP-11814) loadbalancing documentation is unclear
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-11814
loadbalancing documentation is unclear
Change By:
Josh Cooper
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: > {quote} If you're not using HTTP health checks, we recommend using a round robin or random load balancing algorithm for PXP agent {quote} > {quote} 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." {quote} Does that mean for pxp agents "round robin" is recommended" and for puppet agents "least connections"?
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
--
You received this message because you are subs
Jira (PUP-11433) Use systemd provider by default in RHEL/CentOS
Title: Message Title Josh Cooper commented on PUP-11433 Re: Use systemd provider by default in RHEL/CentOS Ticket is in needs information because the PR will cause a regression for RHEL derivative like Rocky and Almalinux. 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.432109.1643027399000.4476.1681243980027%40Atlassian.JIRA.
Jira (PUP-11815) Default system provider to systemd with Amazon Linux 2023
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11815 Default system provider to systemd with Amazon Linux 2023 Change By: Josh Cooper Team: Phoenix 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.484145.1680874387000.4475.1681243920024%40Atlassian.JIRA.
Jira (PUP-11815) Default system provider to systemd with Amazon Linux 2023
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11815 Default system provider to systemd with Amazon Linux 2023 Change By: Josh Cooper Summary: Use Default system provider to systemd for services with Amazon Linux 2023 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.484145.1680874387000.4474.1681243860088%40Atlassian.JIRA.
Jira (PUP-11815) Use systemd for services with Amazon Linux 2023
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-11815
Use systemd for services with Amazon Linux 2023
Change By:
Josh Cooper
*Puppet Version:* 7.24*Puppet Server Version:* None*OS Name/Version:* Amazon Linux 2023 I'm using Puppet 7.24 installed from `[https://yum.puppet.com/puppet7-release-el-9.noarch.rpm]`The same issue reported in PUP-11168 and PUP-11433 also applies for Amazon Linux 2023.When using the service resource type, Amazon Linux 2023 is not listed in {{{}[https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/service/systemd.rb]{}}}, so it falls back to using {{chkconfig}} and {{{}/sbin/service{}}}. {*}Desired Behavior:{*}{*}{{*}}Amazon Linux 2023 should use {{systemd}} for services. *Actual Behavior:*The service resource type in Amazon Linux 2023 falls back to {{chkconfig}} and {{{}/sbin/service{}}}.Let's suppose an example service like this: {code:puppet} service { 'my-service': ensure => 'running', name => 'my-service', enable => true,} {code} When running {{puppet apply}} I get errors from {{chkconfig}} {noformat} Error: Could not enable envoy: Execution of '/sbin/chkconfig --add my-service' returned 1: error reading information on service my-service: No such file or directory Error: /Stage[main]/My_Class/Service[my-service]/ensure: change from 'stopped' to 'running' failed: Could not enable my-service: Execution of '/sbin/chkconfig --add my-service' returned 1: error reading information on service my-service: No such file or directory {noformat} By patching {{/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/systemd.rb}} with: {{defaultfor :operatingsystem => :amazon, :operatingsystemmajrelease => ["2", "2023"]}} the issue appears to be fixed.
Add Comment
Jira (PDB-5613) Drop PSON or at least don't call it by default
Title: Message Title Cas Donoghue assigned an issue to Austin Blatt PuppetDB / PDB-5613 Drop PSON or at least don't call it by default Change By: Cas Donoghue Assignee: Cas Donoghue 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.483168.1679088965000.4345.1681232160022%40Atlassian.JIRA.
Jira (PDB-5612) Update PuppetDB acceptance tests for Platform 8
Title: Message Title Cas Donoghue assigned an issue to Austin Blatt PuppetDB / PDB-5612 Update PuppetDB acceptance tests for Platform 8 Change By: Cas Donoghue 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.482934.1678896009000.4344.1681232100022%40Atlassian.JIRA.
Jira (PUP-7435) Add support for snap packages
Title: Message Title James Paton-Smith commented on PUP-7435 Re: Add support for snap packages Canonical seem to be doubling down on snaps in recent times. They're only going to become more prevalent on Ubuntu, and possibly other distros. I think having some method of managing snap packages through Puppet is a must-have, whether as part of the package type, or something else. What information would be needed to implement this? I see Hadmut Danisch has already linked the relevant API docs, although it has now been moved: https://forum.snapcraft.io/t/snapd-rest-api/17954 Is there any precedent for having a specific package manager as it's own type, rather than part of the packgage type? 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.184760.1491554952000.4244.1681206780020%40Atlassian.JIRA.
