Jira (PUP-1804) Improve testing around \u in puppet language
Title: Message Title Susan McNerney updated an issue Puppet / PUP-1804 Improve testing around \u in puppet language Change By: Susan McNerney Component/s: Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1630) Prepare a gem-only Facter 2.5.0 release
Title: Message Title Josh Cooper commented on FACT-1630 Re: Prepare a gem-only Facter 2.5.0 release Packages are available at http://builds.delivery.puppetlabs.net/facter/2.5.0/. Since this is a gem-only release, I would be fine shipping what we tagged as 2.5.0 (as the gems are not exercised by the acceptance CI changes above). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6764) Add PO files with translated strings to Puppet repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6764 Add PO files with translated strings to Puppet repo Change By: Geoff Nichols Fix Version/s: PUP 5.y Fix Version/s: PUP 5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1630) Prepare a gem-only Facter 2.5.0 release
Title: Message Title Geoff Nichols commented on FACT-1630 Re: Prepare a gem-only Facter 2.5.0 release Merged PR#1604 to facter:2.x at https://github.com/puppetlabs/facter/commit/d4129db5ba9bf0fb8738224250112fe627235322. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7766) Puppet 5.0 Regression: puppet resource with --modulepath no longer loads expected code
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7766 Puppet 5.0 Regression: puppet resource with --modulepath no longer loads expected code Change By: Eric Thompson Labels: regression Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1630) Prepare a gem-only Facter 2.5.0 release
Title: Message Title Melissa Stone commented on FACT-1630 Re: Prepare a gem-only Facter 2.5.0 release the url is malformed. It is currently http://apt.puppetlabs.com//puppetlabs-release-precise.deb when it should be http://apt.puppetlabs.com/puppetlabs-release-precise.deb. But Rob is right. I'm not sure why you'd need the puppetlabs repos just for package acceptance. That, and these are old old repos that haven't been updated in a long time. It's all the pre-puppet-agent stuff Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1630) Prepare a gem-only Facter 2.5.0 release
Title: Message Title Rob Braden commented on FACT-1630 Re: Prepare a gem-only Facter 2.5.0 release But yes, those repos have recently moved into the Cloudfront CDN, which doesn't appear to like the double-forward-slash after the host in http://apt.puppetlabs.com//puppetlabs-release-.deb, removing that works properly. Is that in the job? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1630) Prepare a gem-only Facter 2.5.0 release
Title: Message Title Rob Braden commented on FACT-1630 Re: Prepare a gem-only Facter 2.5.0 release This is just for the gem, right? Then apt shouldn't be in play at all unless I'm misunderstanding something... Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1630) Prepare a gem-only Facter 2.5.0 release
Title: Message Title Maggie Dreyer commented on FACT-1630 Re: Prepare a gem-only Facter 2.5.0 release Seeing a few packaging related failures trying to validate the candidate SHA for this (which I tagged before realizing I should try to validate again): https://jenkins.puppetlabs.com/view/legacy_Facter/view/2.x/job/legacy_facter_integration-system_linux_2.x/ The Redhat 7 failure is due to an upstream dependency getting updated. The most recent code change merged to this branch concerned incrementing the version of this dependency. If this it is really going to be changing this much, that method of tracking it seems brittle. The Ubuntu failures are due to malformed paths attempting to download from http://apt.puppetlabs.com//puppetlabs-release-.deb. Not sure what changed to cause this, possible some changes made by RE around new repos for Platform 5. Morgan Rhodes or Melissa Stone thoughts? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3788) Puppet Agent does not support Chained CRLs
Title: Message Title Karen Van der Veer assigned an issue to Unassigned Puppet / PUP-3788 Puppet Agent does not support Chained CRLs Change By: Karen Van der Veer Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7766) Puppet 5.0 Regression: puppet resource with --modulepath no longer loads expected code
Title: Message Title Maggie Dreyer commented on PUP-7766 Re: Puppet 5.0 Regression: puppet resource with --modulepath no longer loads expected code Personally I feel like the unit tests are enough. I just verified manually that this works. But I do want to qualify that I don't have a good grasp of the subtleties at work here (need to learn more about environments). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7766) Puppet 5.0 Regression: puppet resource with --modulepath no longer loads expected code
Title: Message Title Eric Thompson commented on PUP-7766 Re: Puppet 5.0 Regression: puppet resource with --modulepath no longer loads expected code Josh Cooper, Ethan Brown, Maggie Dreyer, any opinions on if this should be covered in acceptance? i see the unit tests ensuring modulepath is set in static environment use case. does this go far enough to ensure we can load code the way we expect in places like puppet resource? does this need to be tested against env isolation type cases? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7738 "bundle exec puppet module install" fails on Puppet 5.0.0 Change By: Eric Thompson QA Risk Assessment Reason: partially covered by unit tests. should still test in acceptance with semantic_puppet gem installed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Eric Thompson commented on PUP-7738 Re: "bundle exec puppet module install" fails on Puppet 5.0.0 Erik Dasher, this looks like a prime first suspect for automation. bundle install with the Gemfile above (possibly JUST with semantic_puppet?) and bundle exec puppet module install with a version specified. looks like this needs a testrail entry Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Eric Thompson assigned an issue to Erik Dasher Puppet / PUP-7738 "bundle exec puppet module install" fails on Puppet 5.0.0 Change By: Eric Thompson Assignee: qa Erik Dasher Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7766) Puppet 5.0 Regression: puppet resource with --modulepath no longer loads expected code
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-7766 Puppet 5.0 Regression: puppet resource with --modulepath no longer loads expected code Change By: Maggie Dreyer Assignee: qa Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Josh Cooper commented on PUP-7738 Re: "bundle exec puppet module install" fails on Puppet 5.0.0 Awesome, thanks Taylan Develioglu! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7738 "bundle exec puppet module install" fails on Puppet 5.0.0 Change By: Maggie Dreyer Method Found: Needs Assessment Customer Feedback Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7747) Update vendored version of the semantic_puppet gem to version 1.0.1
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7747 Update vendored version of the semantic_puppet gem to version 1.0.1 Change By: Josh Cooper Release Notes Summary: Previously, puppet's vendored semantic_puppet implementation would reject prerelease module versions containing leading zeros with hex digits, e.g. 00abc. This ticket updates the vendored semantic_puppet to accept them, and is the same fix as was applied to the external semantic_puppet gem, see MODULES-5159. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7742) Regression: cannot set file owner to new user when purging unmanaged users
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-7742 Regression: cannot set file owner to new user when purging unmanaged users Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7742) Regression: cannot set file owner to new user when purging unmanaged users
Title: Message Title
Josh Cooper commented on PUP-7742
Re: Regression: cannot set file owner to new user when purging unmanaged users
Verified the above manifest fails in 5.0.0:
[root@vp2vpnqielm4iv5 ~]# facter os
{
architecture => "x86_64",
family => "RedHat",
hardware => "x86_64",
name => "CentOS",
release => {
full => "7.2.1511",
major => "7",
minor => "2"
},
Jira (PUP-7742) Regression: cannot set file owner to new user when purging unmanaged users
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-7742 Regression: cannot set file owner to new user when purging unmanaged users Change By: Josh Cooper Assignee: qa Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7739) Need to regen man pages for 5.0.x
Title: Message Title Josh Cooper commented on PUP-7739 Re: Need to regen man pages for 5.0.x Using puppet-agent#c6fbaa35b07a4b0f384eb4ed94a5a40efd6e91f3: $ man -M /opt/puppetlabs/puppet/share/man/ puppet.conf ... PUPPETCONF(5)Puppet manual PUPPETCONF(5) This page is autogenerated; any changes will get overwritten (last generated on 2017-06-29 14:42:23 -0700) ... $ man -M /opt/puppetlabs/puppet/share/man/ puppet-agent.conf PUPPET-AGENT(8) Puppet manual PUPPET-AGENT(8) NAME
Jira (PUP-7764) Manually test package/service default providers on Amazon Linux
Title: Message Title Branan Riley commented on PUP-7764 Re: Manually test package/service default providers on Amazon Linux I'm concerned that this only indicates that puppet has selected a "barely functional" provider rather than the optimal one. Unfortunately it doesn't look like --debug gives you any info on provider selection when running puppet resource. I think it will require some manual hacking to add debug prints to verify the correct providers have been chosen. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7742) Regression: cannot set file owner to new user when purging unmanaged users
Title: Message Title Branan Riley assigned an issue to qa Puppet / PUP-7742 Regression: cannot set file owner to new user when purging unmanaged users Change By: Branan Riley Status: Ready for CI Test Assignee: Moses Mendoza qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7739) Need to regen man pages for 5.0.x
Title: Message Title Branan Riley assigned an issue to qa Puppet / PUP-7739 Need to regen man pages for 5.0.x Change By: Branan Riley Status: Ready for CI Test Assignee: Josh Cooper qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7766) Puppet 5.0 Regression: puppet resource with --modulepath no longer loads expected code
Title: Message Title Branan Riley assigned an issue to qa Puppet / PUP-7766 Puppet 5.0 Regression: puppet resource with --modulepath no longer loads expected code Change By: Branan Riley Status: Ready for CI Test Assignee: Ethan Brown qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Branan Riley assigned an issue to qa Puppet / PUP-7738 "bundle exec puppet module install" fails on Puppet 5.0.0 Change By: Branan Riley Status: Ready for CI Test Assignee: Josh Cooper qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1676) Acceptance test tests/facts/el.rb fails on Amazon Linux
Title: Message Title Josh Cooper commented on FACT-1676 Re: Acceptance test tests/facts/el.rb fails on Amazon Linux Acceptance passed with os.name Amazon: 14:14:04 ec2-35-163-104-16.us-west-2.compute.amazonaws.com (redhat6-64-2) 14:14:04$ facter os.name 14:14:04 Amazon https://jenkins.puppetlabs.com/view/OPSWORK/job/platform_puppet-agent_intn-van-sys_suite-daily-facter-1.10.x/4/SLAVE_LABEL=beaker,TEST_TARGET=redhat6-64a%257Bamisize=m3.large%252Cvmname=amazon-6-x86_64%252Csnapshot=pe%252Cuser=ec2-user%257D/ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1718) Update acceptance pre-suite for EC2
Title: Message Title Josh Cooper updated an issue Facter / FACT-1718 Update acceptance pre-suite for EC2 Change By: Josh Cooper Fix Version/s: FACT 3.6.6 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1718) Update acceptance pre-suite for EC2
Title: Message Title Josh Cooper commented on FACT-1718 Re: Update acceptance pre-suite for EC2 Verified facter is working as expected with beaker-puppet 0.3.0 released today: https://jenkins.puppetlabs.com/view/OPSWORK/job/platform_puppet-agent_intn-van-sys_suite-daily-facter-1.10.x/4/ Since no facter code changes were required, marking this as a dup of BKR-1159 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (HI-576) Update acceptance pre-suite for EC2
Title: Message Title Josh Cooper commented on HI-576 Re: Update acceptance pre-suite for EC2 Verified hiera is working as expected with beaker-puppet 0.3.0 released today: https://jenkins.puppetlabs.com/view/OPSWORK/job/platform_puppet-agent_intn-van-sys_suite-daily-hiera-1.10.x/5/ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1588) Building with openssl 1.1.0 fails
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1588 Building with openssl 1.1.0 fails Change By: Kenn Hussey Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Reid Vandewiele commented on PUP-5934 Re: Updated fact values should be submitted after each Puppet run +1 to Nick Walker's point. I am strongly in favor of PUP-7779 and think we need it. This ticket most naturally then becomes an improvement request to be built on top of PUP-7779. PUP-7779 is not an alternate solution; it's a prerequisite. If "won't fix" is still correct for this ticket, can you please provide more background information about the decision? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7782) execpipe raises method error if the command fails with no output
Title: Message Title Ethan Brown commented on PUP-7782 Re: execpipe raises method error if the command fails with no output We considered calling to_s inside of lib/puppet/error.rb but decided against it. The message parameter is supposed to be a string, not an arbitrary object. We decided we'd rather have callers be responsible for stringify'ing their messages properly, rather than blindly relying on to_s (which in some cases produces a Ruby object id instead of something useful) - and if they raise, then we know inappropriate calls are being made. I did a quick audit of the Puppet code at the time and found that the only offender was the code we fixed. See the comment at https://github.com/puppetlabs/puppet/pull/6066#issuecomment-314935158 for some more notes. /cc Moses Mendoza Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1651) facter tests failures on power 8 on Ubuntu 16.04 and Rhel 7
Title: Message Title Scott Garman updated an issue Facter / FACT-1651 facter tests failures on power 8 on Ubuntu 16.04 and Rhel 7 Change By: Scott Garman Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7774) Acceptance tests/resource/package/common_package_name_in_different_providers.rb fails in Amazon Linux
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7774 Acceptance tests/resource/package/common_package_name_in_different_providers.rb fails in Amazon Linux Change By: Geoff Nichols Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7774) Acceptance tests/resource/package/common_package_name_in_different_providers.rb fails in Amazon Linux
Title: Message Title
Geoff Nichols commented on PUP-7774
Re: Acceptance tests/resource/package/common_package_name_in_different_providers.rb fails in Amazon Linux
Passing CI run at https://jenkins.puppetlabs.com/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-1.10.x/SLAVE_LABEL=beaker,TEST_TARGET=redhat6-64a%257Bamisize=m3.large%252Cvmname=amazon-6-x86_64%252Csnapshot=pe%252Cuser=ec2-user%257D/8/consoleFull
Confirmed test is skipped when running on Amazon Linux in EC2:
22:25:15 tests/resource/mount/query.rb passed in 1.09 seconds
22:25:15 Begin tests/resource/package/common_package_name_in_different_providers.rb
22:25:15
22:25:15 ticket 1073: common package name in two different providers should be allowed
22:25:15 Warning: No suitable hosts without: {:hypervisor=>"ec2"}
22:25:15
22:25:15 No suitable hosts found without {:hypervisor=>"ec2"}
22:25:15 Begin teardown
22:25:15 End teardown
Jira (PUP-7752) Acceptance test tests/resource/service/service_enable_linux.rb fails on Amazon Linux
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7752 Acceptance test tests/resource/service/service_enable_linux.rb fails on Amazon Linux Change By: Geoff Nichols Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7772) Puppet fails to create error message when an exec fails
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7772
Puppet fails to create error message when an exec fails
Change By:
Josh Cooper
Release Notes Summary:
Puppet 4.10.1 and 5.0.0 introduced a regression if a provider called {{execpipe}} and the external command failed. This ticket fixes puppet so that it correctly processes the execution failure.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-7772) Puppet fails to create error message when an exec fails
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7772
Puppet fails to create error message when an exec fails
Change By:
Josh Cooper
Release Notes Summary:
Puppet 5.0.0 introduced a regression if a provider called {{execpipe}} and the external command failed. This ticket fixes puppet so that it correctly processes the execution failure.
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-7772) Puppet fails to create error message when an exec fails
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-7772
Puppet fails to create error message when an exec fails
Change By:
Josh Cooper
Release Notes Summary:
Puppet 4.10. 1 2 and 5.0.0 introduced a regression if a provider called {{execpipe}} and the external command failed. This ticket fixes puppet so that it correctly processes the execution failure.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-7782) execpipe raises method error if the command fails with no output
Title: Message Title Josh Cooper commented on PUP-7782 Re: execpipe raises method error if the command fails with no output Thanks Les Aker I'll close this as a dup of PUP-7771. Puppet 5.0.1 is due out tomorrow or the next day depending how things go. Ethan Brown thoughts about the comment Les Aker made about calling to_s instead of the ExceptionFailure class. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7739) Need to regen man pages for 5.0.x
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7739 Need to regen man pages for 5.0.x Change By: Josh Cooper Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7738 "bundle exec puppet module install" fails on Puppet 5.0.0 Change By: Josh Cooper Release Notes Summary: Puppet 5.0.0 introduced a regression when running "puppet module install" via bundler. This issue only occurred if the Gemfile directly or indirectly expressed a dependency on the "semantic_puppet" gem. A common way for this to happen was if the module's Gemfile relied on the "metadata-json-lint" gem, which depends on "semantic_puppet". This fix ensures puppet works correctly when using either the external "semantic_puppet" gem or the vendored version in Puppet. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7599) Acceptance: Fix authorized keys acceptance tests
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7599 Acceptance: Fix authorized keys acceptance tests Change By: Maggie Dreyer Fix Version/s: PUP 4.10.5 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3606) puppetdb upgrade from 4.1.2 to any newer version timeout
Title: Message Title
Rob Browning commented on PDB-3606
Re: puppetdb upgrade from 4.1.2 to any newer version timeout
Thanks for the update – If you have time, could you also see what your table sizes are? i.e. connect to your database via psql ("psql puppetdb") or something similar, and see what \dt+ reports?
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-7521) Puppet Acceptance Test Failure in Imaging Acceptance Tests
Title: Message Title John O'Connor assigned an issue to Eric Delaney Puppet / PUP-7521 Puppet Acceptance Test Failure in Imaging Acceptance Tests Change By: John O'Connor Assignee: John O'Connor Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7521) Puppet Acceptance Test Failure in Imaging Acceptance Tests
Title: Message Title John O'Connor commented on PUP-7521 Re: Puppet Acceptance Test Failure in Imaging Acceptance Tests Eric Delaney, I have run this through the imaging pipeline and the following tests pass ok: tests/reports/corrective_change_new_resource.rb tests/reports/corrective_change_outside_puppet.rb tests/reports/corrective_change_via_puppet.rb tests/resource/file/ticket_6448_file_with_utf8_source.rb Unfortunately test tests/catalog_with_binary_data.rb fails with a similar error: 05:40:58 cmd.exe /c puppet agent -t --environment ticket_6448_file_with_utf8_source_omtbnwaq --server duaytgmfihwjgou 05:40:58 Last 10 lines of output were: 05:40:58 Info: Using configured environment 'ticket_6448_file_with_utf8_source_omtbnwaq' 05:40:58 Info: Retrieving pluginfacts 05:40:58 Info: Retrieving plugin 05:40:58 Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: No matching entry for selector parameter with value
Jira (FACT-1720) regression on overidding external facts (shell)
Title: Message Title Franck Jouvanceau created an issue Facter / FACT-1720 regression on overidding external facts (shell) Issue Type: Bug Affects Versions: FACT 3.6.5, FACT 3.6.3 Assignee: Unassigned Components: CLI Created: 2017/07/17 8:16 AM Environment: OS : RedHat 7.2, RedHat 6.5 Puppet : puppet-agent-1.10.4 (puppet 4.10.4) puppet-agent-1.10.0 (puppet 4.10.1) Priority: Normal Reporter: Franck Jouvanceau overidding shell external facts (facts.d) using shell variable FACTER_fact does not work anymore. (is working with puppet 3.8.5) cat /tmp/puppet/facts.d/ext_fact.sh #!/bin/ksh -p echo "ext_fact=from_script"
Jira (FACT-1651) facter tests failures on power 8 on Ubuntu 16.04 and Rhel 7
Title: Message Title Kenn Hussey commented on FACT-1651 Re: facter tests failures on power 8 on Ubuntu 16.04 and Rhel 7 Scott Garman please provide release notes for this issue, if applicable. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7742) Regression: cannot set file owner to new user when purging unmanaged users
Title: Message Title Kenn Hussey commented on PUP-7742 Re: Regression: cannot set file owner to new user when purging unmanaged users Moses Mendoza please provide release notes for this issue, if needed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7740) Enable acceptance pre-suite to install puppetserver on EC2
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7740 Enable acceptance pre-suite to install puppetserver on EC2 Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Kenn Hussey commented on PUP-7738 Re: "bundle exec puppet module install" fails on Puppet 5.0.0 Josh Cooper please provide release notes for this issue, if needed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7739) Need to regen man pages for 5.0.x
Title: Message Title Kenn Hussey commented on PUP-7739 Re: Need to regen man pages for 5.0.x Josh Cooper please provide release notes for this issue, if needed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7747) Update vendored version of the semantic_puppet gem to version 1.0.1
Title: Message Title Kenn Hussey commented on PUP-7747 Re: Update vendored version of the semantic_puppet gem to version 1.0.1 Thomas Hallgren please provide release notes for this issue, if needed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7772) Puppet fails to create error message when an exec fails
Title: Message Title Kenn Hussey commented on PUP-7772 Re: Puppet fails to create error message when an exec fails Josh Cooper please provide release notes for this issue, if needed. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7782) execpipe raises method error if the command fails with no output
Title: Message Title Les Aker commented on PUP-7782 Re: execpipe raises method error if the command fails with no output I think it may make more sense to call .to_s inside util/puppet/error.rb, since otherwise things that derive from Puppet::Error will still behave in a non-standard way, and so we'll run into this anywhere else that somebody raises one of those errors with a non-string 2nd param, but you are correct that this does fix the problem I was experiencing. I'm not super familiar with Puppet's release cadence; would you be able to provide a gut guess for how far off 5.0.1 is? Essentially, I'm currently hand-patching this on a few systems to get around the bug, and trying to decide if it's worth doing something fancier or if I should just hold out on upgrading other systems until 5.0.1 is available. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7738) "bundle exec puppet module install" fails on Puppet 5.0.0
Title: Message Title Taylan Develioglu commented on PUP-7738 Re: "bundle exec puppet module install" fails on Puppet 5.0.0 Josh Cooper Can confirm this fixes the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
