Jira (PUP-9088) Build Puppet Agent for Ubuntu 18.10
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9088 Build Puppet Agent for Ubuntu 18.10 Change By: Mihai Buzgau Sprint: PR - 2018-08-29, PR - 2018-09-12, PR - 2018-09-26, PR - 2018-10-10, 2018-10-24 , 2018-11-07 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-968) Document available Bolt transports
Title: Message Title Abir Majumdar created an issue Puppet Task Runner / BOLT-968 Document available Bolt transports Issue Type: Task Assignee: Unassigned Created: 2018/11/07 9:09 AM Labels: DOCS Priority: Normal Reporter: Abir Majumdar From HipChat: A customer was asking me if bolt could be run over the puppet protocol. So I wanted to send the link to the docs, and a direct answer was harder to find than expected. First, I expected a pcp example in the "Running basic Bolt commands" but there isn't one. Next, under Transport under "Bolt command reference" the list of acceptable values for '--transport' aren't listed. Similarly, under "Set a default transport" under "Adding options to Bolt commands" pcp isn't mentioned. There is the page "Configuring Bolt to use orchestrator" but if I'm new to Puppet I have no idea what the "orchestrator" is (it's also buried under Configuring Bolt). Available transports are listed in the `bolt --help` output, but not the docs. Add Comment
Jira (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title David Kramer assigned an issue to Michael Smith Puppet Task Runner / BOLT-459 Reboot a target and wait for it to become available. Change By: David Kramer Assignee: Michael Smith 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-965) Create alpine-based image
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-965 Create alpine-based image Change By: David Kramer Labels: puppercon 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-962) docker transport
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-962 docker transport Change By: David Kramer Labels: puppercon 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-966) Configure bolt-server from environment variables
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-966 Configure bolt-server from environment variables Change By: David Kramer Labels: puppercon 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-967) Publish to PCR per-commit to Bolt
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-967 Publish to PCR per-commit to Bolt Change By: David Kramer Labels: puppercon 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-941) Publish apply_helpers to forge and document it's installation
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-941 Publish apply_helpers to forge and document it's installation Change By: Michael Smith To use apply with pcp nodes apply_helpers needs to be installed. It should be published to forge and documentation on using Bolt with Orchestrator updated for it. 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-964) Containerize bolt-server
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-964 Containerize bolt-server Change By: David Kramer Labels: puppercon 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-459) Reboot a target and wait for it to become available.
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-459 Reboot a target and wait for it to become available. Change By: Michael Smith Assignee: Michael Smith 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-9304) Puppet::Util::Execution.execute does not have binary-safe stdinfile support
Title: Message Title Sean Millichamp created an issue Puppet / PUP-9304 Puppet::Util::Execution.execute does not have binary-safe stdinfile support Issue Type: Bug Assignee: Unassigned Created: 2018/11/07 10:56 AM Priority: Normal Reporter: Sean Millichamp While working on a patch to address SERVER-2167 I was trying to pass binary data on stdin to a command (gpg) run by Puppet::Util::Execution.execute using the stdinfile option. GPG was returning errors indicating the input data was corrupted so I did some digging. I believe that the 'r' in this line https://github.com/puppetlabs/puppet/blob/d4348e02c5eba0222d400ab0883f53cc8e2a086f/lib/puppet/util/execution.rb#L199 should be 'rb' to indicate to Ruby that the encoding should be treated as ASCII-8BIT instead of the default (in my environment UTF-8). It should be safe to pass binary data in via execute's stdinfile option and if the current behavior cannot be changed then there should be an option which indicates that stdinfile should be treated as binary data. In this instance, I was able to work around the issue by passing the file directly to gpg as a command line argument instead of using stdinfile (and it worked), but it may not be possible to do that in every use case. My testing was within Puppetserver in PE 2018.1.3. Add Comment
Jira (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title Lucy Wyman commented on BOLT-459 Re: Reboot a target and wait for it to become available. I wasn't able to get the reboot plan working on Windows <= 8.1. It worked as expected on newer Windows versions, as well as centos and ubuntu. 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-9305) Built-in unique function behaves differently with undef
Title: Message Title Erik Hansen created an issue Puppet / PUP-9305 Built-in unique function behaves differently with undef Issue Type: Bug Assignee: Unassigned Created: 2018/11/07 11:34 AM Priority: Normal Reporter: Erik Hansen The unique function introduced in PUP-7620 introduces a possible breaking change, as it behaves differently than the stdlib function when passed an undef value. Reproduction: With the following manifest, unique.pp: $unique = unique($this_is_undef) notice($unique) With stdlib installed (puppet apply unique.pp): Warning: Unknown variable: 'this_is_undef'. at /root/unique.pp:1:22 Notice: Scope(Class[main]): Notice:
Jira (PUP-9305) Built-in unique function behaves differently with undef
Title: Message Title
Erik Hansen updated an issue
Puppet / PUP-9305
Built-in unique function behaves differently with undef
Change By:
Erik Hansen
The unique function introduced in PUP-7620 introduces a possible breaking change, as it behaves differently than the stdlib function when passed an undef value.h5. Reproduction:With the following manifest, unique.pp: {code:java} $unique = unique($this_is_undef)notice($unique){code}With stdlib installed (puppet apply unique.pp):{code:java} Warning: Unknown variable: 'this_is_undef'. at /root/unique.pp:1:22Notice: Scope(Class[main]): Notice: Compiled catalog for pe-2016413-master.puppetdebug.vlan in environment production in 0.19 secondsNotice: Applied catalog in 0.33 seconds{code}Without stdlib installed:{code:java} Warning: Unknown variable: 'this_is_undef'. (file: /root/unique.pp, line: 1, column: 22)Error: Evaluation Error: Error while evaluating a Function Call, 'unique' expects one of: (String string, Callable[String] block?) rejected: parameter 'string' expects a String value, got Undef (Hash hash, Callable[Any] block?) rejected: parameter 'hash' expects a Hash value, got Undef (Array array, Callable[Any] block?) rejected: parameter 'array' expects an Array value, got Undef (Iterable iterable, Callable[Any] block?) rejected: parameter 'iterable' expects an Iterable value, got Undef (file: /root/unique.pp, line: 1, column: 15) on node pe-201813-master.puppetdebug.vlan{code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9306) Regression in heredoc parser in 5.5.8
Title: Message Title
Adam Bottchen created an issue
Puppet / PUP-9306
Regression in heredoc parser in 5.5.8
Issue Type:
Bug
Affects Versions:
PUP 5.5.8
Assignee:
Unassigned
Created:
2018/11/07 11:40 AM
Priority:
Major
Reporter:
Adam Bottchen
Puppet Version: 5.5.8 Puppet Server Version: N/A OS Name/Version: N/A Starting with Puppet 5.5.8, previously working code now fails to validate or compile:
$text = @("EOT")
foo=${a}(value="${h['v']}")
|EOT
Desired Behavior: This code should validate and compile normally. Actual Behavior:
# puppet parser validate test.pp
Jira (PDB-4157) Review impact of connection limits in clj-http-client
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4157 Review impact of connection limits in clj-http-client Change By: Rob Browning Assignee: Rob Browning 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-9306) Regression in heredoc parser in 5.5.8
Title: Message Title Henrik Lindberg commented on PUP-9306 Re: Regression in heredoc parser in 5.5.8 This is the same as PUP-9303 which has the full explanation. I fix is coming shortly. Closing this as a duplicate, but will test the sample in here as well. 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-9306) Regression in heredoc parser in 5.5.8
Title: Message Title Henrik Lindberg commented on PUP-9306 Re: Regression in heredoc parser in 5.5.8 Before the commit that was mentioned above, the problem would simply move such that it would look at another (seemingly random) position and it probably finds a non space there - that is why the snippet in this ticket then "works" - but it would break if moved or margin of the heredoc is changed. PUP-9303 will have the full fix for this problem. 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-9305) Built-in unique function behaves differently with undef
Title: Message Title Henrik Lindberg commented on PUP-9305 Re: Built-in unique function behaves differently with undef We can make the unique function in core return undef when getting an undef value, although it is strange to call unique in the first place on an undef value (since something has probably gone wrong?). It works in the stdlib version since undef is given to a 3.x function as an empty string and unique constructs a new string with unique characters from that string - so the result is an empty string. It would be strange if the core unique function returned an empty string when given an undef value, but returning undef or possibly an empty array would be fine. PUP-7620 added the core unique function for Puppet 5.0.0 so technically it is allowed to break API (even if this was unintentional). Erik Hansen Is it ok to fix this by returning undef for undef ? 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-9305) Built-in unique function behaves differently with undef
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-9305 Built-in unique function behaves differently with undef Change By: Henrik Lindberg Assignee: Henrik Lindberg 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 (PDB-4157) Review impact of connection limits in clj-http-client
Title: Message Title Rob Browning commented on PDB-4157 Re: Review impact of connection limits in clj-http-client I think I may have been mistaken (looking for the wrong thing), so I'll check again. 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-9305) Built-in unique function behaves differently with undef
Title: Message Title Erik Hansen commented on PUP-9305 Re: Built-in unique function behaves differently with undef Henrik Lindberg - undef for undef is I think what we want, since that's what the stdlib function does – unless you think this is an issue with my code that was masked by the stdlib version? Some added context - we originally saw this in some acceptance testing which caused a hard failure with the new function, the stdlib function would pass the test without issues. More context here: https://github.com/puppetlabs/puppet_metrics_dashboard/pull/11 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.
