Jira (PUP-9597) Send release announcement (Puppet Platform 5.5.13)
Title: Message Title Eric Griswold assigned an issue to Sara Meisburger Puppet / PUP-9597 Send release announcement (Puppet Platform 5.5.13) Change By: Eric Griswold Assignee: Eric Griswold Sara Meisburger Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9639) Windows package resource does not remove trailing whitespace
Title: Message Title Eric Thompson updated an issue Puppet / PUP-9639 Windows package resource does not remove trailing whitespace Change By: Eric Thompson Fix Version/s: PUP 5.5.14 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9472) Use OpenSSL::X509::Name#to_utf8
Title: Message Title Jean Bond updated an issue Puppet / PUP-9472 Use OpenSSL::X509::Name#to_utf8 Change By: Jean Bond Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9047) puppet device --apply fails to apply catalog to unregistered targets pt. 2
Title: Message Title Jean Bond updated an issue Puppet / PUP-9047 puppet device --apply fails to apply catalog to unregistered targets pt. 2 Change By: Jean Bond Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8213) Error message for certificate name mismatch is clear as mud
Title: Message Title Kris Bosland commented on PUP-8213 Re: Error message for certificate name mismatch is clear as mud Merged into 6.4.x at 8876131. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9470) Add note to logs about which value we're getting the server from
Title: Message Title Jean Bond updated an issue Puppet / PUP-9470 Add note to logs about which value we're getting the server from Change By: Jean Bond Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8036) Use of server_list can cause misleading agent errors
Title: Message Title Jean Bond updated an issue Puppet / PUP-8036 Use of server_list can cause misleading agent errors Change By: Jean Bond Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1914) Expose Facter.reset under jruby
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1914 Expose Facter.reset under jruby Change By: Geoff Nichols Fix Version/s: FACT 3.13.z Fix Version/s: FACT 3.13.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9641) Puppet Master Installation on FIPS enabled RHEL fails
Title: Message Title Matt Mason created an issue Puppet / PUP-9641 Puppet Master Installation on FIPS enabled RHEL fails Issue Type: Bug Affects Versions: PUP 5.5.10 Assignee: Unassigned Created: 2019/04/12 12:22 PM Priority: Critical Reporter: Matt Mason Puppet Version: 5.5.10 Puppet Server Version: 2018.1.7 OS Name/Version: RHEL 7.6 Immediately after a successful installation/upgrade of Puppet 2018.1.7 on a FIPS enabled RHEL7.6 system, running puppet agent -t on the master node fails with the following error: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Unable to generate package repository configuration. Platform described by facts['platform_tag'] 'redhatfips-7-x86_64' is not a known master platform. (file: /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/repo/config.pp, line: 158, column: 9) This issue isn't observed after a successful installation of Puppet 2019.0.1 in the same configuration. Desired Behavior: **Puppet installation of the LTS branch should not have an issue installing on FIPS enabled systems. Actual Behavior: Using Puppet facts show on the system in the two different configurations (2018 and 2019) shows the platform_tag fact to be identical in both configurations when FIPS mode is enabled for the system: "platform_tag": "redhatfips-7-x86_64",
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Eric Thompson Assignee: Sean McDonald Eric Thompson Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1196) bolt-inventory-pdb examples in public documentation are incorrect
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1196 bolt-inventory-pdb examples in public documentation are incorrect Change By: Cas Donoghue Labels: bolt documentation docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1196) bolt-inventory-pdb examples in public documentation are incorrect
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1196 bolt-inventory-pdb examples in public documentation are incorrect Change By: Cas Donoghue Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1196) bolt-inventory-pdb examples in public documentation are incorrect
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1196 bolt-inventory-pdb examples in public documentation are incorrect Change By: Cas Donoghue Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9565) Not possible to set Mutliple Logging Destination with puppet agent anymore
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9565 Not possible to set Mutliple Logging Destination with puppet agent anymore Change By: Josh Cooper Fix Version/s: PUP 6.0.9 Fix Version/s: PUP 5.5.14 Fix Version/s: PUP 6.4.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9565) Not possible to set Mutliple Logging Destination with puppet agent anymore
Title: Message Title Josh Cooper commented on PUP-9565 Re: Not possible to set Mutliple Logging Destination with puppet agent anymore Verified it writes to multiple log destinations: $ rm /tmp/puppet.log $ bx puppet agent --no-daemonize --detailed-exitcodes --onetime --logdest console --logdest /tmp/puppet.log --verbose Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Caching catalog for localhost Info: Applying configuration version '1555090905' Notice: Applied catalog in 0.10 seconds $ cat /tmp/puppet.log 2019-04-12 10:41:20 -0700 Puppet (notice): Applied catalog in 0.07 seconds 2019-04-12 10:41:42 -0700 Puppet (info): Using configured environment 'production' 2019-04-12 10:41:42 -0700
Jira (BOLT-1142) Following bolt installation instructions on a PE node can be dangerous
Title: Message Title Joshua Partlow commented on BOLT-1142 Re: Following bolt installation instructions on a PE node can be dangerous From the perspective of PE's installer tooling, the agent version is fixed between installations; nothing manages the puppet-agent version until the next run of the installer script from the next version PE tarball. But if a repo source has more recent versions of puppet-agent and someone uses the package manager, for, say an os upgrade (PE-26356), then the agent can get upgraded unexpectedly, potentially breaking PE. (Mostly adding this note for my own reference and to tie the two tickets together). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9565) Not possible to set Mutliple Logging Destination with puppet agent anymore
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9565 Not possible to set Mutliple Logging Destination with puppet agent anymore Change By: Josh Cooper Fix Version/s: PUP 6.4.z Fix Version/s: PUP 6.0.z Fix Version/s: PUP 5.5.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9565) Not possible to set Mutliple Logging Destination with puppet agent anymore
Title: Message Title Josh Cooper commented on PUP-9565 Re: Not possible to set Mutliple Logging Destination with puppet agent anymore Merged in 5.5.x in https://github.com/puppetlabs/puppet/commit/00dcdf2fdbbc2d15564998db4441e269b899c3df Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-265) @example doesn't work with 4.x functions
Title: Message Title Jean Bond commented on PDOC-265 Re: @example doesn't work with 4.x functions Good catch, Henrik Lindberg, that might be part of the issue. I've PR'd a fix to that. There's still a lot of other descriptive text not getting picked up, but maybe this will fix the example issue. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-843) Generate a "rerun" file after every command
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-843 Generate a "rerun" file after every command Change By: Cas Donoghue Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1194) Validate simple plans
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1194 Validate simple plans Change By: Cas Donoghue When a plan is loaded we should perform the following validation:- All required keys for all steps are present- Puppet code snippets parse as valid code- No unexpected keys (for each step as well as top level plan) - unique and valid step/parameter names (already implemented in 1.15.0) Note that when using CLI plan is loaded twice. Once when we do parameter validation https://github.com/puppetlabs/bolt/blob/7751b4e82cd723527a137560d00f9be29771aeaf/lib/bolt/cli.rb#L271And again when it is run https://github.com/puppetlabs/bolt/blob/7751b4e82cd723527a137560d00f9be29771aeaf/lib/bolt/cli.rb#L379 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1244) SELinux management does not work on localhost
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1244
SELinux management does not work on localhost
Change By:
Alex Dreyer
It looks like the SELinux bindings are not packaged with bolt and therefore don't work when the localhost target attempts to execute a catalog in bolt's ruby environment. We should probably evaluate all diffferences between what ships with bolt and the agent now that we try to use bolt's ruby in place of the agent's. Example:{noformat}`apply(localhost) { `file { '/var/www/myapp':` `ensure => directory,` `owner => 'nginx',` `group => 'nginx',` `mode=> '0755',` `seltype => 'httpd_sys_rw_content_t',` `recurse => true` `}`}{noformat}Workaround for version > 1.16.0Target {{local://nomagic}} to avoid using bolt's ruby.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop
Jira (BOLT-1244) SELinux management does not work on localhost
Title: Message Title
Alex Dreyer created an issue
Puppet Task Runner / BOLT-1244
SELinux management does not work on localhost
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/04/12 8:54 AM
Priority:
Normal
Reporter:
Alex Dreyer
It looks like the SELinux bindings are not packaged with bolt and therefore don't work when the localhost target attempts to execute a catalog in bolt's ruby environment. Example:
`apply(localhost) {
`file { '/var/www/myapp':`
`ensure => directory,`
`owner => 'nginx',`
`group => 'nginx',`
`mode=> '0755',`
`seltype =>
Jira (PDOC-265) @example doesn't work with 4.x functions
Title: Message Title Henrik Lindberg commented on PDOC-265 Re: @example doesn't work with 4.x functions Examples in regsubst.rb (the 4.x implementation) looks like this: # @example Get the third octet from the node's IP address: # # ```puppet # $i3 = regsubst($ipaddress,'^(\\d+)\\.(\\d+)\\.(\\d+)\\.(\\d+)$','\\3') # ``` # # @example Put angle brackets around each octet in the node's IP address: # # ```puppet # $x = regsubst($ipaddress, /([0-9]+)/, '<\\1>', 'G') # ``` Note that the example body is one blank line away and not indented. Is that what is causing Puppet Strings to not pick it up? Or is it something else?
Jira (PDB-4343) Docker: Set puppetdb alt names via environment
Title: Message Title Alexander Heimann created an issue PuppetDB / PDB-4343 Docker: Set puppetdb alt names via environment Issue Type: New Feature Affects Versions: PDB 6.3.0 Assignee: Unassigned Created: 2019/04/12 12:17 AM Priority: Normal Reporter: Alexander Heimann We need the ability to set Alt Names for the Certificate in the PuppetDB Container. Also the ability to set the jetty option ssl-cert-chain in the jetty.ini would be good. We are using a SubCA for our environment wich needs to supply the complete chain to the client. Add Comment
