Jira (PUP-6464) Template search behavior changed from v3 to v4
Title: Message Title
Brian Sipos updated an issue
Puppet / PUP-6464
Template search behavior changed from v3 to v4
Change By:
Brian Sipos
I have been attempting to migrate a puppet server v3 configuration to v4 test host. I have been following the recommended steps at [https://docs.puppet.com/puppet/latest/reference/upgrade_major_server.html]. Most of the modules and classes seem to migrate okay, but I'm seeing a strange issue in the use of a templated file. I have defined a custom module which is simply a "files" and "templates" subdirectory tree, to which I reference files from my {{site.pp}} directly in the form of {{... content => template('local-data/app/file.erb') ... }}.This worked fine in v3 but appears to not work in v4. I have tried to troubleshoot how puppet is searching for template files, but I have hit a dead-end and my knowledge of Ruby is very limited. Is this kind of template use supported in v4? Defining the files from within a module and referencing them directly from {{site.pp}} rather than the module itself?
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6464) Template search behavior changed from v3 to v4
Title: Message Title
Brian Sipos created an issue
Puppet / PUP-6464
Template search behavior changed from v3 to v4
Issue Type:
Bug
Affects Versions:
PUP 4.5.2
Assignee:
Unassigned
Components:
Puppet Server
Created:
2016/06/30 8:43 PM
Environment:
CentOS-7 x86_64
Priority:
Normal
Reporter:
Brian Sipos
I have been attempting to migrate a puppet server v3 configuration to v4 test host. I have been following the recommended steps at https://docs.puppet.com/puppet/latest/reference/upgrade_major_server.html. Most of the modules and classes seem to migrate okay, but I'm seeing a strange issue in the use of a templated file. I have defined a custom module which is simply a "files" and "templates" subdirectory tree, to which I reference files from my site.pp directly in the form of {{... content => template('local-data/app/file.erb') ... }}. This worked fine in v3 but appears to not work in v4. I have tried to troubleshoot how puppet is searching for template files, but I have hit a dead-end and my knowledge of Ruby is
Jira (PUP-6383) Acceptance: test that failover information is added to the report
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-6383
Acceptance: test that failover information is added to the report
Change By:
Maggie Dreyer
Acceptance Criteria:
Acceptance test to verify that:* the correct master is listed in the report when failover functionality is used* no master is listed if not using failover
The report will specify which master was successfully used (See PUP-6378). The actual key in the report has the following specification:{noformat}" master master_used ": {"description": "The name and port of the master that was used to compile the catalog. If failover occurred, this will hold the first master successfully contacted. If this run had no master (e.g. a `puppet apply` run), this field will be blank", "type": "string" },{noformat}Write a test similar to {{tests/reports/cached_catalog_status_in_report.rb}} to check the report..
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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
Jira (PUP-2362) ssh_authorized_keys temporary file Operation not permitted
Title: Message Title
Dan Alvizu commented on PUP-2362
Re: ssh_authorized_keys temporary file Operation not permitted
We've worked around this with 'file' and file_line' resources:
ssh_authorized_key{ $name :
key => $userdata_hash[$name]['key'],
type=> 'ssh-rsa',
user=> $name,
name=> $email,
}
File[$home] -> File["${home}/.ssh"] -> Ssh_authorized_key[$name]
Replaced with:
file{ "${home}/.ssh/authorized_keys" :
Jira (PDB-2849) correct deprecation warning around export tool
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2849 correct deprecation warning around export tool Change By: Wyatt Alt Fix Version/s: PDB 4.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2849) correct deprecation warning around export tool
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2849 correct deprecation warning around export tool Issue Type: Bug Assignee: Unassigned Created: 2016/06/30 3:18 PM Priority: Normal Reporter: Wyatt Alt Currently we report this: [deprecated] The PuppetDB export command is deprecated in favor of exports via the Puppet 'db' subcommand. See 'man puppet-db' for usage instructions. BUT [root@large-mom ~]# puppet db Error: Unknown Puppet subcommand 'db'
Jira (PUP-6376) Add `server_urls` option to puppet with agent failover logic
Title: Message Title Eric Thompson commented on PUP-6376 Re: Add `server_urls` option to puppet with agent failover logic acceptance test coming, this sprint. resolving... Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6415) static_compiler: symlinks in recursed directories don't work
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6415 static_compiler: symlinks in recursed directories don't work Change By: Eric Thompson QA Risk Assessment: Medium Low Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-4809) Yumrepo type says uppercase values are allowed when they are not
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-4809 Yumrepo type says uppercase values are allowed when they are not Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6463) Accessing a required parameter that is unassigned causes bad error message
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6463 Accessing a required parameter that is unassigned causes bad error message Change By: Henrik Lindberg Acceptance Criteria: If a parameter default _expression_ references an earlier parameter and that referenced parameter is not given a value, the error message should state that the required parameter has not been given a value. Story Points: 1 Summary: Second Accessing a required parameter that is evaluated first unassigned causes bad error message Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6463) Accessing a required parameter that is unassigned causes bad error message
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6463 Accessing a required parameter that is unassigned causes bad error message Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6463) Second parameter is evaluated first
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6463 Second parameter is evaluated first Change By: Henrik Lindberg Release Notes Summary: If a parameter default _expression_ referenced an earlier parameter and that referenced parameter was not given a value, a bad error message would state that this reference was illegal. Now it correctly reports the actual error of a required parameter not having been given a value. Sprint: Language Triage Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6463) Second parameter is evaluated first
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6463 Second parameter is evaluated first Change By: Henrik Lindberg Fix Version/s: PUP 4.5.4 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6463) Second parameter is evaluated first
Title: Message Title Henrik Lindberg commented on PUP-6463 Re: Second parameter is evaluated first Yeah that error message is not the best. It should be able to figure out that the referenced parameter is unassigned rather than illegally referenced. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6463) Second parameter is evaluated first
Title: Message Title
Josh Samuelson created an issue
Puppet / PUP-6463
Second parameter is evaluated first
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/06/30 12:56 PM
Priority:
Normal
Reporter:
Josh Samuelson
I ran into this error trying to include a PE profile class that happened to inherit a class that was already defined in the PE console. This is the minimal repro of the root issue.
Given the following site.pp:
class breaking (
String $first,
String $second = $first,
){}
Jira (PUP-5626) empty dependencies in a module break puppet module tool for unrelated modules
Title: Message Title Nick Walker updated an issue Puppet / PUP-5626 empty dependencies in a module break puppet module tool for unrelated modules Change By: Nick Walker Priority: Normal Minor Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5626) empty dependencies in a module break puppet module tool for unrelated modules
Title: Message Title
Nick Walker commented on PUP-5626
Re: empty dependencies in a module break puppet module tool for unrelated modules
Ben Ford can you update the description / title? Based on the comments it sounds like the ask here is to improve the error handling of PMT when there a dependencies array is not specified.
Realistically `puppet module generate` provides a dependencies array with stdlib in it so I think this should be pretty rare.
[root@master-no-pe-centos ~]# cat /root/blah/metadata.json
{
"name": "npwalker-blah",
"version": "0.1.0",
"author": "npwalker",
"summary": null,
"license": "Apache-2.0",
"source": "",
"project_page": null,
"issues_url": null,
Jira (PDB-2848) Investigate http-client sync retrieval performance
Title: Message Title Rob Browning created an issue PuppetDB / PDB-2848 Investigate http-client sync retrieval performance Issue Type: Improvement Assignee: Unassigned Created: 2016/06/30 12:58 PM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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
Jira (PUP-6463) Second parameter is evaluated first
Title: Message Title Josh Samuelson updated an issue Puppet / PUP-6463 Second parameter is evaluated first Change By: Josh Samuelson Affects Version/s: PUP 4.5.2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5982) Acceptance: add test case for 'parser validate'
Title: Message Title John Duarte assigned an issue to Unassigned Puppet / PUP-5982 Acceptance: add test case for 'parser validate' Change By: John Duarte Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5982) Acceptance: add test case for 'parser validate'
Title: Message Title John Duarte assigned an issue to Eric Sorenson Puppet / PUP-5982 Acceptance: add test case for 'parser validate' Change By: John Duarte Assignee: John Duarte Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5604) Add journalctl command when service fails for systemd
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5604 Add journalctl command when service fails for systemd Change By: Eric Thompson Release Notes Summary: the systemd service provider now asks journalctl why something failed and reports it back to the user for aid in debugging. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1449) Facter does not honor digits as Strings
Title: Message Title Peter Huene updated an issue Facter / FACT-1449 Facter does not honor digits as Strings Change By: Peter Huene Affects Version/s: FACT 3.1.8 Story Points: 1 Release Notes Summary: Facter treated quoted numeric and boolean values in YAML external fact files as numeric/boolean instead of respecting the quotes and treating the value as a string. Facter has been fixed to only perform the conversion for unquoted scalar values. Sprint: Client Triage Scrum Team: Client Platform Release Notes: Bug Fix Fix Version/s: FACT 3.3.0 Add Comment
Jira (PUP-5604) Add journalctl command when service fails for systemd
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5604 Add journalctl command when service fails for systemd Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1449) Facter does not honor digits as Strings
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-1449 Facter does not honor digits as Strings Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5604) Add journalctl command when service fails for systemd
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5604 Add journalctl command when service fails for systemd Change By: Eric Thompson Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5604) Add journalctl command when service fails for systemd
Title: Message Title
Eric Thompson commented on PUP-5604
Re: Add journalctl command when service fails for systemd
validated against puppet agent master sha: 2e1f658732ca423ee43860cb3a7ce7b2c549938e on rhel7 with
[root@sp87at98x02dtjk ~]# puppet apply journalctl.pp
Notice: Compiled catalog for sp87at98x02dtjk.delivery.puppetlabs.net in environment production in 0.17 seconds
Error: Execution of 'journalctl -n 50 --since '5 minutes ago' -u foo --no-pager' returned 1: -- Logs begin at Thu 2016-06-30 09:41:12 PDT, end at Thu 2016-06-30 12:13:11 PDT. --
Error: /Stage[main]/Main/Service[foo]/ensure: change from stopped to running failed: Execution of 'journalctl -n 50 --since '5 minutes ago' -u foo --no-pager' returned 1: -- Logs begin at Thu 2016-06-30 09:41:12 PDT, end at Thu 2016-06-30 12:13:11 PDT. --
Notice: Applied catalog in 0.05 seconds
[root@sp87at98x02dtjk ~]# cat journalctl.pp
service { 'foo':
ensure => running,
start => '/usr/bin/systemctl start foo'
Jira (FACT-1449) Facter does not honor digits as Strings
Title: Message Title Peter Huene commented on FACT-1449 Re: Facter does not honor digits as Strings Found this issue on yaml-cpp: https://github.com/jbeder/yaml-cpp/issues/261 Checking to see if the tag could be used to resolve this. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1449) Facter does not honor digits as Strings
Title: Message Title Peter Huene commented on FACT-1449 Re: Facter does not honor digits as Strings This is a problem in the underlying yaml-cpp library Facter uses to parse YAML. The problem is that, internally, scalar data is stored as strings, even for non-string scalars (numbers, booleans, etc). Facter attempts to use yaml-cpp's API for converting the scalar's value to a double, integer, or boolean. If the scalar data is convertible, then Facter treats the value as having that type. Thus, strings like 'true', 'false', '123', and '123.456' will all be converted to a non-string type. Given the yaml-cpp API, there is no way to prevent this from occurring other than treating all scalar values read in from a yaml file as string values. This is even less desired than the behavior described in this ticket, however. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1449) Facter does not honor digits as Strings
Title: Message Title Ranjit Viswakumar created an issue Facter / FACT-1449 Facter does not honor digits as Strings Issue Type: Bug Assignee: Unassigned Created: 2016/06/30 11:54 AM Priority: Normal Reporter: Ranjit Viswakumar Have a partner on site with a module that require's a String input. The String is a series of digits however. Facter is making it a Fixnum. [root@master ~]# cat /etc/puppetlabs/facter/facts.d/string.yaml --- thing: string: '123'
Jira (PUP-5604) Add journalctl command when service fails for systemd
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-5604 Add journalctl command when service fails for systemd Change By: Eric Thompson Assignee: qa Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5921) Deprecate source_permissions
Title: Message Title William Hopper updated an issue Puppet / PUP-5921 Deprecate source_permissions Change By: William Hopper Scope Change Reason: brought on for onboarding , but we realized it was blocked on another ticket so we took it back out Sprint: Client 2016-07-13 (HA, 1.5.3) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6390) Acceptance: unpin run order for service_enable_linux test
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-6390 Acceptance: unpin run order for service_enable_linux test Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6390) Acceptance: unpin run order for service_enable_linux test
Title: Message Title Eric Thompson commented on PUP-6390 Re: Acceptance: unpin run order for service_enable_linux test merged to stable. should be merged up to master when CI passes Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6376) Add `server_urls` option to puppet with agent failover logic
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-6376 Add `server_urls` option to puppet with agent failover logic Change By: Eric Thompson Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6411) Puppet 3.x fails acceptance on Ubuntu precise
Title: Message Title Eric Thompson commented on PUP-6411 Re: Puppet 3.x fails acceptance on Ubuntu precise and again: https://jenkins.puppetlabs.com/job/legacy_puppet_integration-system_linux_3.x/lastCompletedBuild/label=beaker,platform=precise/testReport/(root)/tests/allow_arbitrary_node_name_fact_for_agent_rb/ Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6458) puppet 3.x tests failing with undefined method `upcase' in route.rb
Title: Message Title Eric Thompson commented on PUP-6458 Re: puppet 3.x tests failing with undefined method `upcase' in route.rb yep. looks the same to me. same platform. wasn't aware of it. it's transient? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-71) Stack Level Too Deep Exception and Spurious Errors
Title: Message Title Hailee Kenney commented on PDOC-71 Re: Stack Level Too Deep Exception and Spurious Errors So unfortunately I had to time box my work on the issue and after some poking around in the debugger I still haven't been able to get to the root of it. I figured I'd leave some notes on where I was planning on going next for my future self or whoever picks up this ticket. I think this is going to be kind of a hairy issue to track down judging by the fact that it only happens at a particular scale and that this file evaluated on its own is fine. I think, as the ticket description suggests, that it's a fair assumption something is being corrupted somewhere. That being said, comparing our code object in the good case and the code object in the bad case may be the key to tracking things down. Since the exception is occurring in the HostClassHandler the object in question is this one. I think either inspecting this object with the debugger or printing it in both scenarios (a. running it in the batch when it fails and b. running it on it's own when it passes) and seeing what is different should point to where the corruption is potentially happening. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6458) puppet 3.x tests failing with undefined method `upcase' in route.rb
Title: Message Title Branan Riley commented on PUP-6458 Re: puppet 3.x tests failing with undefined method `upcase' in route.rb maybe PUP-6411? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-4660) Stop checking Puppet.features.external_facts?
Title: Message Title Andrew Henroid updated an issue Puppet / PUP-4660 Stop checking Puppet.features.external_facts? Change By: Andrew Henroid Scope Change Category: Adopted Scope Change Reason: onboarding Sprint: Client 2016-07-13 (HA, 1.5.3) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5921) Deprecate source_permissions
Title: Message Title Andrew Henroid assigned an issue to Andrew Henroid Puppet / PUP-5921 Deprecate source_permissions Change By: Andrew Henroid Assignee: Andrew Henroid Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-4660) Stop checking Puppet.features.external_facts?
Title: Message Title Andrew Henroid assigned an issue to Andrew Henroid Puppet / PUP-4660 Stop checking Puppet.features.external_facts? Change By: Andrew Henroid Assignee: Andrew Henroid Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6458) puppet 3.x tests failing with undefined method `upcase' in route.rb
Title: Message Title Branan Riley commented on PUP-6458 Re: puppet 3.x tests failing with undefined method `upcase' in route.rb Isn't this the issue we've been tracking approximately forever at this point? This may be a duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5921) Deprecate source_permissions
Title: Message Title Andrew Henroid updated an issue Puppet / PUP-5921 Deprecate source_permissions Change By: Andrew Henroid Scope Change Category: Adopted Scope Change Reason: onboarding Sprint: Client 2016-07-13 (HA, 1.5.3) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6462) Re-enable links to filebucket diffs in the console
Title: Message Title Brian Conner commented on PUP-6462 Re: Re-enable links to filebucket diffs in the console Thank you Erik Hansen. To be clear, we'd like the hashes under "changed from" and "changed to" to be clickable to see both the before and after if possible. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6461) pip package provider with "ensure => latest" displays version change when there is none (problem parsing the output string in some cases)
Title: Message Title Branan Riley updated an issue Puppet / PUP-6461 pip package provider with "ensure => latest" displays version change when there is none (problem parsing the output string in some cases) Change By: Branan Riley Labels: client-onboarding Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6462) Re-enable links to filebucket diffs in the console
Title: Message Title Erik Hansen updated an issue Puppet / PUP-6462 Re-enable links to filebucket diffs in the console Attaching screenshot Change By: Erik Hansen Attachment: Screen Shot 2016-06-30 at 9.35.22 AM.png Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6462) Re-enable links to filebucket diffs in the console
Title: Message Title Erik Hansen created an issue Puppet / PUP-6462 Re-enable links to filebucket diffs in the console Issue Type: Improvement Assignee: Unassigned Created: 2016/06/30 9:40 AM Priority: Normal Reporter: Erik Hansen In PE 3.8.x you used to be able to find a link to filebucket diffs in the reporting tab. This was useful for troubleshooting and for tracking down what file changes had been made. The link would show up in the the events tab for a changed node under Reports. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title Michael Smith updated an issue Puppet / PUP-6459 puppet resource service fails on Windows 10 Pro (x64) Change By: Michael Smith Affects Version/s: PUP 4.5.2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6460) The addition of dig to puppet functions breaks puppetlabs-stdlib
Title: Message Title Henrik Lindberg commented on PUP-6460 Re: The addition of dig to puppet functions breaks puppetlabs-stdlib I can imagine adding default value support to puppet's dig, but it would still be different. Also reluctant to do that since there is a perfectly composable solution with then() and lest() for the simple case of default value and for other more advanced things. Suggest deprecating the 3.x dig function, and not running the stdlib dig tests when puppet is >= 4.5.0. There cannot be many users of that function. We did something similar for the clash in the type function, where the solution was to add a type3x to stdlib for backwards compatibility. The same could be done here for those few that want to continue using the stdlib 3.x dig. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6461) pip package provider with "ensure => latest" displays version change when there is none (problem parsing the output string in some cases)
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6461 pip package provider with "ensure => latest" displays version change when there is none (problem parsing the output string in some cases) Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6383) Acceptance: test that failover information is added to the report
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-6383 Acceptance: test that failover information is added to the report Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6453) Produced capabilities are evaluated before the component
Title: Message Title Alex Dreyer commented on PUP-6453 Re: Produced capabilities are evaluated before the component That is true. We have to decide whether we want produce statements to be based purely on facts, and external data/classification. If that is the case we should move produce evaluation before any class is evaluated. Right now the behavior is inconsistent since the included class may or may not have been evaluated first. Give the natural semantics of 'produce' it's also counter-intuitive and leads to unexpected bugs when moving components around. The problem that led me to this is a data problem not that I really need the class evaluated. Let me see if I can solve it with lookup. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6461) pip package provider with "ensure => latest" displays version change when there is none (problem parsing the output string in some cases)
Title: Message Title
Diego Abelenda created an issue
Puppet / PUP-6461
pip package provider with "ensure => latest" displays version change when there is none (problem parsing the output string in some cases)
Issue Type:
Bug
Affects Versions:
PUP 4.5.2
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
2016/06/30 7:14 AM
Environment:
Debian Jessie pip 1.5.6
Priority:
Minor
Reporter:
Diego Abelenda
When using package {'virtualenv': ensure => latest, provider => 'pip', }
The return string from " pip install --upgrade virtualenv " is """ Installed version (15.0.2) is most up-to-date (past versions: 15.0.2, 15.0.2, 15.0.1, 15.0.1, 15.0.0, 15.0.0, 14.0.6, 14.0.6, 14.0.5, 14.0.5, 14.0.4, 14.0.4, 14.0.3, 14.0.3, 14.0.2, 14.0.2, 14.0.1, 14.0.1, 14.0.0, 14.0.0, 13.1.2, 13.1.2, 13.1.1, 13.1.1, 13.1.0, 13.1.0, 13.0.3, 13.0.3, 13.0.2, 13.0.2, 13.0.1, 13.0.1, 13.0.0, 13.0.0, 12.1.1, 12.1.1, 12.1.0, 12.1.0, 12.0.7, 12.0.7, 12.0.6, 12.0.5, 12.0.5, 12.0.4, 12.0.4, 12.0.2, 12.0.2, 12.0.1, 12.0.1, 12.0, 12.0,
Jira (PUP-6457) Mount resources could handle invalid options better
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-6457 Mount resources could handle invalid options better Change By: Hailee Kenney Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2847) Spike out threadpool approach to initial sync
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-2847 Spike out threadpool approach to initial sync Issue Type: New Feature Assignee: Unassigned Created: 2016/06/30 6:12 AM Priority: Normal Reporter: Ryan Senior When submitting a new command to PuppetDB, we include a generated UUID and when done processing that command, we put that UUID on a response channel. This approach was needed in the ActiveMQ world as we were using ActiveMQ message listeners as our threadpool. That will not be the case in the future. We should spike out the possibility of changing our approach to initial sync so that it bypasses the queue. We can also reduce the complexity of our solution by providing a direct call to POST N commands. By doing this before the HA work completes, we can avoid some rework needed in the future if we rip out these response channels (which seems pretty likely). Add Comment
Jira (PUP-6460) The addition of dig to puppet functions breaks puppetlabs-stdlib
Title: Message Title Thomas Honey commented on PUP-6460 Re: The addition of dig to puppet functions breaks puppetlabs-stdlib I agree this is not easy to fix, we can fudge the tests to pass. But the difference in functionality / output is the real problem. If both functions perform identically it becomes less of an issue. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6453) Produced capabilities are evaluated before the component
Title: Message Title David Lutterkort commented on PUP-6453 Re: Produced capabilities are evaluated before the component If I understand this right though it would require that the underlying component gets evaluated before we can evaluate the produced resource, right ? IOW, it would make it impossible to evaluate produced resources when we compile the environment catalog without compiling a good part of the node catalogs, too ? That seems like a significant change to me that we won't be able to ever undo and we need to make sure that we are ok with committing to that mode of compilation. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6460) The addition of dig to puppet functions breaks puppetlabs-stdlib
Title: Message Title Henrik Lindberg commented on PUP-6460 Re: The addition of dig to puppet functions breaks puppetlabs-stdlib The missing documentation for new functions have been addressed. The documentation will be there for puppet 4.6.0. (There are capabilities missing in the internal docs processing pipeline). The work on dig, then, lest was done before the dig was added to stdlib. It is an unfortunate clash and the APIs are unfortunately not compatible. dig($data, 1,2,3) vs. dig($data, [1,2,3], 'default'). Have a hard time coming up with something that would make it possible to support both signatures with one function. Not sure what the best action is. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6460) The addition of dig to puppet functions breaks puppetlabs-stdlib
Title: Message Title Thomas Honey created an issue Puppet / PUP-6460 The addition of dig to puppet functions breaks puppetlabs-stdlib Issue Type: Bug Affects Versions: PUP 4.5.2, PUP 4.5.1, PUP 4.5.0 Assignee: Unassigned Components: Language Created: 2016/06/30 2:44 AM Priority: Major Reporter: Thomas Honey With puppet 4.5.X we have introduced dig as a function. This is not documented @ https://docs.puppet.com/puppet/latest/reference/function.html When running puppetlabs-stdlib dig with puppet 4, it uses puppets dig function not stdlib. This is causing weird behaviour, also breaking the acceptance tests for the module. To replicate: checkout the puppetlabs stdlib module. export PUPPET_GEM_VERSION="= 4.5.0" bundle install --path .bundle/gems/
Jira (PUP-6268) Display cert information when interacting with certs via `puppet cert` application
Title: Message Title Kevin Corcoran assigned an issue to Justin Stoller Puppet / PUP-6268 Display cert information when interacting with certs via `puppet cert` application Change By: Kevin Corcoran Assignee: Justin Stoller Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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.
