Jira (PUP-3530) Pass array to custom define fails
Title: Message Title
Wannes Van Causbroeck commented on an issue
Re: Pass array to custom define fails
Hi, we're running: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] Red Hat Enterprise Linux Server release 6.5 (Santiago)
Basically, what i'm trying to do (as the guy in the previous example is doing), is to give an array of hashes as an parameters to a resource i defined myself. I don't know if this is even allowed in puppet, but the weird thing is that it sometimes works and sometimes it doesn't. If i run the following piece of code:
functions.pp class autofs::functions {
$full = hiera($hostname) $mounts = $full[mounts] $links = $full[links]
$def_full = hiera(def_mounts) $def_mounts = $def_full[mounts]
define link () { $dst = $name[dst] $src = "" class="error">[src]
exec { mkdir -p $ {dst}: unless = [ -d ${dst}
] || [ -L $ {dst} ], path = [ /bin, /usr/bin ] } file { $dst: ensure = link, target = $name[src], require = EXEC[mkdir -p ${dst}
], force = true } } file { /etc/auto.nas: owner = root, group = root, mode = 644, content = template(autofs/auto.nas.erb), notify = Service[autofs], }
link { $links: }
}
autofs.yaml —
perms_glu: -fstype=glusterfs
def_mounts: mounts:
dvdimages -fstype=glusterfs lpr-nas01:/dvdimages
ldv-puppetdev01: mounts:
Jira (PUP-3549) Debian init script status and stop actions are unsafe
Title: Message Title Tomasz Kuzemko created an issue Puppet / PUP-3549 Debian init script status and stop actions are unsafe Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Kylo Ginsberg Attachments: puppet.initd.patch Components: Client Created: 27/Oct/14 5:28 AM Environment: Debian/Ubuntu OS and derivatives Labels: puppet-agent Priority: Normal Reporter: Tomasz Kuzemko Calling /etc/init.d/puppet stop does not guarantee that the process being stopped is actually puppet agent process.
Jira (PDB-885) PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-885 PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber Change By: Kenneth Barber Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3550) Issue with manually issuing manually submitting certificate request over API
Title: Message Title Viktor Petersson created an issue Puppet / PUP-3550 Issue with manually issuing manually submitting certificate request over API Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Unassigned Created: 27/Oct/14 6:57 AM Priority: Normal Reporter: Viktor Petersson This is a cross-post from ServerFault. I reached out to James Turnbull, who I believe was involved in the development of this. He thought it was a bug, so, I'm posting it here. The tl;dr is that I need to manually generate a certificate on one node, and then issue a certificate request over the API. According to the documentation, this should be rather straight forward. Here's what I did. Generate a certificate for myhost.foobar.local (from client) $ puppet cert generate myhost.foobar.local Generate a CSR from the certificate (from client)
Jira (PDB-885) PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber kbarber commented: This is now waiting on a release of beaker, probably a 1.21.0. Add Comment PuppetDB / PDB-885 PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber h2. Add VPC support for acceptance test hosts for PuppetDB * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1087 Discussion|https://github.com/puppetlabs/puppetdb/pull/1087] * [Pull Request 1087 File Diff|https://github.com/puppetlabs/puppetdb/pull/1087/files] h2. Pull R... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/138/ Add Comment PuppetDB / PDB-990 PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt h2. Ticket/master/pdb 954 fallback acceptance * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129] * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files] h2. Pull Request Description (webhooks-id... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PDB-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/139/ Add Comment PuppetDB / PDB-990 PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt h2. Ticket/master/pdb 954 fallback acceptance * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129] * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files] h2. Pull Request Description (webhooks-id... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PDB-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt wkalt commented: @pljenkinsro retest this please Add Comment PuppetDB / PDB-990 PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt h2. Ticket/master/pdb 954 fallback acceptance * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129] * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files] h2. Pull Request Description (webhooks-id... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-970) PR (150): Allow only TLS - Fixes POODLE CVE-2014-3566 - ghoneycutt
Title: Message Title gepetto-bot commented on an issue Re: PR (150): Allow only TLS - Fixes POODLE CVE-2014-3566 - ghoneycutt kbarber commented: @ghoneycutt ping, see my previous comment. Add Comment PuppetDB / PDB-970 PR (150): Allow only TLS - Fixes POODLE CVE-2014-3566 - ghoneycutt h2. Allow only TLS - Fixes POODLE CVE-2014-3566 * Author: Garrett Honeycutt git...@garretthoneycutt.com * Company: * Github ID: [ghoneycutt|https://github.com/ghoneycutt] * [Pull Request 150 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/150] * [Pull Request 150 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/1... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-885) PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/137/ Add Comment PuppetDB / PDB-885 PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber h2. Add VPC support for acceptance test hosts for PuppetDB * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 1087 Discussion|https://github.com/puppetlabs/puppetdb/pull/1087] * [Pull Request 1087 File Diff|https://github.com/puppetlabs/puppetdb/pull/1087/files] h2. Pull R... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-3549) Debian init script status and stop actions are unsafe
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Debian init script status and stop actions are unsafe
Matthaus Owens or Melissa Stone thoughts?
Tomasz Kuzemko can you submit this as a pull request at github.com/puppetlabs/puppet?
Add Comment
Puppet / PUP-3549
Debian init script status and stop actions are unsafe
Calling {{/etc/init.d/puppet stop}} does not guarantee that the process being stopped is actually puppet agent process. {{start-stop-daemon}} will kill any process which PID happens to be the same as the one stored in {{/var/run/puppet/agent.pid}}. The same applies to {{/etc/init.d/puppet status}}. It calls {{status_of_proc}} internally, but that does ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PDB-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/140/ Add Comment PuppetDB / PDB-990 PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt h2. Ticket/master/pdb 954 fallback acceptance * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129] * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files] h2. Pull Request Description (webhooks-id... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-3479) Windows ffi dependency fails for Ruby 2.1.3
Title: Message Title Rob Reynolds commented on an issue Re: Windows ffi dependency fails for Ruby 2.1.3 Does this need one for hiera as well? Add Comment Puppet / PUP-3479 Windows ffi dependency fails for Ruby 2.1.3 Ruby 2.1.x was released on Windows for the first time with Ruby 2.1.3 in September: https://www.ruby-forum.com/topic/5768030 Running Ruby from source on Windows with Ruby 2.1.3 fails, because ffi 1.9.3 isn't compatible with Ruby 2.1.x. The ffi dependency needs to be updated to require ffi 1.9.5+ on all our projects that depend on it: at least puppet, f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3130) Remove hidden $_timestamp fact
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-3130 Remove hidden $_timestamp fact Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3130) Remove hidden $_timestamp fact
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3130 Remove hidden $_timestamp fact Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3541) Remove client and server yaml directories
Title: Message Title
Josh Cooper commented on an issue
Re: Remove client and server yaml directories
I think the reason for separate directories is to handle the agent and master running on the same host.
Add Comment
Puppet / PUP-3541
Remove client and server yaml directories
Currently, some data that puppet saves is written to the {{yamldir}} (or {{clientyamldir}}) if it is YAML or to {{server_datadir}} (or {{client_datadir}}) if it is not. All data needs to be written to {{server_datadir}} for the master and {{client_datadir}} for the client, no matter if it is YAML or not. The {{yamldir}} settings can then be removed. ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3516) Puppet breaks on 32-bit Windows XP
Title: Message Title
Josh Cooper commented on an issue
Re: Puppet breaks on 32-bit Windows XP
Bjrn Stabel Yep, we discovered this issue in
PUP-2889
as part of the 3.7.0 release. I submitted a patch upstream https://github.com/djberg96/win32-eventlog/pull/10, which has been merged, but the author only recently published a fix with that fix: https://rubygems.org/gems/win32-eventlog/versions/0.6.2
In the meantime, we patched our vendored ruby gems for 3.7.0 in:
https://github.com/puppetlabs/puppet-win32-ruby/pull/44 https://github.com/puppetlabs/puppet-win32-ruby/pull/46
So this should only be an issue if you are running puppet from source, e.g. bundle exec, or testing a module on XP/2003.
Now that the new win32-eventlog gem has been released, we need to update our gem dependencies and remove our patch from our vendored ruby gem. That work is being tracked in PUP-3061, so I'm going to close this as a duplicate.
Add Comment
Puppet / PUP-3516
Puppet breaks on 32-bit Windows XP
The new win32-eventlog version that Puppet is using is looking for {{Wow64DisableWow64FsRedirection}}. However, that only exists in {{kernel.dll}} on Windows XP 64bit Edition and Vista and upwards. This currently results in Puppet exploding on 'normal' Windows XP: {noformat} C:/Programme/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/ffi-1.9
Jira (PUP-3514) Future parser not showing line/column for error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3514 Future parser not showing line/column for error Change By: Henrik Lindberg Sprint: PlatformServer2014-10-29 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3541) Remove client and server yaml directories
Title: Message Title
Andy Parker commented on an issue
Re: Remove client and server yaml directories
I think so too. I took a look in the directories on my machine (where I often run the server and agent together) and it didn't look like they would collide. I think we can just go ahead and keep the separate for now unless someone discovers that there is really no good reason to keep the separate.
Add Comment
Puppet / PUP-3541
Remove client and server yaml directories
Currently, some data that puppet saves is written to the {{yamldir}} (or {{clientyamldir}}) if it is YAML or to {{server_datadir}} (or {{client_datadir}}) if it is not. All data needs to be written to {{server_datadir}} for the master and {{client_datadir}} for the client, no matter if it is YAML or not. The {{yamldir}} settings can then be removed. ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (PUP-3514) Future parser not showing line/column for error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3514 Future parser not showing line/column for error Change By: Henrik Lindberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3498) Create rubygem confine for use with providers
Title: Message Title Josh Cooper commented on an issue Re: Create rubygem confine for use with providers Reid Vandewiele This should work today. Define a feature that is true if the gem can be loaded: Puppet.features.add(:somegem, :libs = [somegem]) And then confine your provider: confine :feature = :somegem From https://docs.puppetlabs.com/guides/provider_development.html#suitability As of 2.7.20, Puppet will enable the provider if the feature becomes available during a run (i.e. a package is installed). If this isn't working correctly, let us know. Add Comment Puppet / PUP-3498 Create rubygem confine for use with providers
Jira (PUP-3498) Create rubygem confine for use with providers
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3498 Create rubygem confine for use with providers Change By: Josh Cooper Assignee: ReidVandewiele Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3498) Create rubygem confine for use with providers
Title: Message Title Reid Vandewiele commented on an issue Re: Create rubygem confine for use with providers Ben Ford, does this work for your use case? Josh Cooper, is it appropriate to define features in a provider, or should feature definition ideally be limited to the type? iirc, the use case that spawned this ticket was creating a customer provider for an existing type, or a type not under the control of the provider author. Add Comment Puppet / PUP-3498 Create rubygem confine for use with providers Currently, if a provider requires a particular rubygem to be installed in order to function, it is difficult to indicate, or confine, that provider to systems that have the gem installed WHILE allowing in-run installation of the gem. E.g. have Puppet pluginsync down a new mount provider, my_provider, from a module, and specify a package resource, with the... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-3498) Create rubygem confine for use with providers
Title: Message Title Josh Cooper commented on an issue Re: Create rubygem confine for use with providers Reid Vandewiele You should be able to just put the feature definition in your module. From that same page, You can also create your own custom feature. They live in lib/puppet/feature/*.rb ... These features can be shipped in a similar manner as types and providers are shipped within modules and will be pluginsynced. Add Comment Puppet / PUP-3498 Create rubygem confine for use with providers Currently, if a provider requires a particular rubygem to be installed in order to function, it is difficult to indicate, or confine, that provider to systems that have the gem installed WHILE allowing in-run installation of the gem. E.g. have Puppet pluginsync down a new mount provider, my_provider, from a module, and specify a package resource, with the... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-3479) Windows ffi dependency fails for Ruby 2.1.3
Title: Message Title Rob Reynolds commented on an issue Re: Windows ffi dependency fails for Ruby 2.1.3 Facter merged into master at 2b71211. This should split off to a different ticket to be tracked with facter 2.3 Add Comment Puppet / PUP-3479 Windows ffi dependency fails for Ruby 2.1.3 Ruby 2.1.x was released on Windows for the first time with Ruby 2.1.3 in September: https://www.ruby-forum.com/topic/5768030 Running Ruby from source on Windows with Ruby 2.1.3 fails, because ffi 1.9.3 isn't compatible with Ruby 2.1.x. The ffi dependency needs to be updated to require ffi 1.9.5+ on all our projects that depend on it: at least puppet, f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3479) Windows ffi dependency fails for Ruby 2.1.3
Title: Message Title Josh Cooper commented on an issue Re: Windows ffi dependency fails for Ruby 2.1.3 As Michael Smith discovered, neither facter nor hiera make FFI calls, so they should not depend on ffi directly. However, it's not clear that all of the win32 gems that puppet, facter, and hiera depend on express their FFI dependencies correctly, and bundler may have issues resolving transitive dependencies with platform specific gems. For example, bundle install may resolve facter win32 * - ffi, but select the generic ffi gem that requires the devkit to be installed, instead of the platform specific ffi-x86-mingw32 gem. If neither of those things are issues anymore, we could remove the ffi dependency from facter (Hiera already doesn't specify an dependency on ffi). Add Comment Puppet / PUP-3479 Windows ffi dependency fails for Ruby 2.1.3 Ruby 2.1.x was released on Windows for the first time with Ruby 2.1.3 in September: https://www.ruby-forum.com/topic/5768030 Running Ruby from source on Windows with Ruby 2.1.3 fails, because ffi 1.9.3 isn't compatible with Ruby 2.1.x. The ffi dependency needs to be updated to require ffi 1.9.5+ on all our projects that depend on it: at least puppet, f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3272) Remove support for yaml on the network
Title: Message Title
Henrik Lindberg commented on an issue
Re: Remove support for yaml on the network
Afaict there was only one place where the special deserialization was needed (handling of tags in Status), and it now implements the Psych specific method via inclusion of a module (to make it stand out and also to be reusable if there are additional cases where it is needed).
PR 3240 submitted for review.
Add Comment
Puppet / PUP-3272
Remove support for yaml on the network
YAML on the network is either dangerous or slow. It is dangerous without safe_yaml and slow with it. We've had it deprecated for a while now. Puppet 4 is the time to completely remove it. We can remove: * vendored safe_yaml * serializing and deserializing yaml * special parsing for query parameters that start with {{\-\-\-}} * more?
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (PUP-1106) Resource refreshes don't check for failed dependencies
Title: Message Title
Adrien Thebo commented on an issue
Re: Resource refreshes don't check for failed dependencies
Andy Parker are you still reviewing this issue or can we unassign it so that someone else may review it?
Add Comment
Puppet / PUP-1106
Resource refreshes don't check for failed dependencies
Given this manifest: {code} exec{moo: command = /usr/bin/cowsay 'fail :(', refreshonly = true, logoutput = true, require = Exec[false], subscribe = [ File[/tmp/1], File[/tmp/2], File[/tmp/3] ] } file{/tmp/1: content = 1} file{/tmp/2: content = 2} file{/tmp/3: content = 3} exec{false: command...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2609) Don't allow source_permissions to be set to anything other than ignore on Windows
Title: Message Title
Rob Reynolds commented on an issue
Re: Don't allow source_permissions to be set to anything other than ignore on Windows
Merged into master at a52294f
Add Comment
Puppet / PUP-2609
Don't allow source_permissions to be set to anything other than ignore on Windows
When we added the source_permissions attribute in Puppet 3.4, we marked the values {{:use}} and {{:use_when_creating}} as deprecated on Windows, since it basically wreaks havoc at all times. The 4.0 boundary is a good time to follow through on that deprecation and make setting these values to anything other than {{:ignore}} an error on Windows
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3498) Create rubygem confine for use with providers
Title: Message Title Reid Vandewiele commented on an issue Re: Create rubygem confine for use with providers That looks awesome. I don't think I'd really seen features and how they're used prior to reading through this. Ben Ford, what do you think? Add Comment Puppet / PUP-3498 Create rubygem confine for use with providers Currently, if a provider requires a particular rubygem to be installed in order to function, it is difficult to indicate, or confine, that provider to systems that have the gem installed WHILE allowing in-run installation of the gem. E.g. have Puppet pluginsync down a new mount provider, my_provider, from a module, and specify a package resource, with the... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3471 Windows Puppet x86 Installer on x64 system issue Change By: Rob Reynolds Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3471 Windows Puppet x86 Installer on x64 system issue Change By: Rob Reynolds Sprint: PlatformClient2014-10-29 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3471 Windows Puppet x86 Installer on x64 system issue Change By: Rob Reynolds Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3516) Puppet breaks on 32-bit Windows XP
Title: Message Title
Rob Reynolds commented on an issue
Re: Puppet breaks on 32-bit Windows XP
Windows XP is not a supported platform. Windows Server 2003 is a supported platform however.
Add Comment
Puppet / PUP-3516
Puppet breaks on 32-bit Windows XP
The new win32-eventlog version that Puppet is using is looking for {{Wow64DisableWow64FsRedirection}}. However, that only exists in {{kernel.dll}} on Windows XP 64bit Edition and Vista and upwards. This currently results in Puppet exploding on 'normal' Windows XP: {noformat} C:/Programme/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/ffi-1.9
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3530) Pass array to custom define fails
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Pass array to custom define fails
Thanks for the additional info!
So, the issue here is that the title of a resource is expected to be a string or an array of strings. Overloading the title by passing in a hash of data, instead of adding parameters to a type, is not guaranteed to work and future versions of the Puppet language may throw an error for this case.
Your link defined type should declare parameters for src and dst instead of picking them out of name:
define link (
$src,
$dst,
) {
exec { mkdir -p ${dst}:
unless = [ -d ${dst} ] || [ -L ${dst} ],
path = [ /bin, /usr/bin ]
}
file { $dst:
Jira (PDB-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/141/ Add Comment PuppetDB / PDB-990 PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt h2. Ticket/master/pdb 954 fallback acceptance * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129] * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files] h2. Pull Request Description (webhooks-id... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PDB-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt kbarber commented: @pljenkinsro retest this please Add Comment PuppetDB / PDB-990 PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt h2. Ticket/master/pdb 954 fallback acceptance * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129] * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files] h2. Pull Request Description (webhooks-id... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3479) Windows ffi dependency fails for Ruby 2.1.3
Title: Message Title Michael Smith commented on an issue Re: Windows ffi dependency fails for Ruby 2.1.3 My only concern with removing FFI from facter is ensuring I can test it sufficiently. If the main problem is bundle and Jenkins jobs, I can give it a try and see if we break anything. Add Comment Puppet / PUP-3479 Windows ffi dependency fails for Ruby 2.1.3 Ruby 2.1.x was released on Windows for the first time with Ruby 2.1.3 in September: https://www.ruby-forum.com/topic/5768030 Running Ruby from source on Windows with Ruby 2.1.3 fails, because ffi 1.9.3 isn't compatible with Ruby 2.1.x. The ffi dependency needs to be updated to require ffi 1.9.5+ on all our projects that depend on it: at least puppet, f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2706) Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Title: Message Title
Melissa Stone commented on an issue
Re: Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Kenneth Barber you might want to wait until the PR is merged, but that's up to you
Add Comment
Puppet / PUP-2706
Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
We keep getting this error during Puppet installation for our PuppetDB builds: {code} Setting up ruby-augeas (0.5.0-2) ... Setting up libaugeas-ruby (0.5.0-2) ... Setting up ruby-shadow (2.2.0-1) ... Setting up ruby-json (1.8.0-1build1) ... Setting up hiera (1.3.3-1puppetlabs1) ... Setting up puppet-common (3.6.1-1puppetlabs1) ... chage: the sha...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1208) md5lite, mtime not honoured for file type/provider
Title: Message Title
Mark Schmick commented on an issue
Re: md5lite, mtime not honoured for file type/provider
Ping … when will a Fix Version be assigned? This is egregious since checksum is now broken for anything but md5. And since that's the default, you might as well say using checksum breaks file resources, since if you use it at all to override md5, you always get a mis-match because the server only does md5. For example:
file { chroot-20070718.tar:
ensure = present,
path = ${release_account::redhat::home}/chroot-20070718.tar,
source = /root/puppet/modules/release_account/files/chroots/${::osfamily}/chroot-20070718.tar,
checksum = sha256lite,
}
Results in:
Notice: /Stage[main]/Release_account::Redhat::Chroot/File[chroot-20070718.tar]/content: current_value
{sha256lite}3b155333d1cb1ed4e96f791c16dda06d95c47ded1b206240ed61c2c09f1426ba, should be
Jira (PUP-2976) File { checksum = .. } doesn't work
Title: Message Title
Mark Schmick commented on an issue
Re: File { checksum = .. } doesn't work
Ping … when will a Fix Version be assigned? This is egregious since checksum is now broken for anything but md5. And since that's the default, you might as well say using checksum breaks file resources, since if you use it at all to override md5, you always get a mis-match because the server only does md5. For example:
file { chroot-20070718.tar:
ensure = present,
path = ${release_account::redhat::home}/chroot-20070718.tar,
source = /root/puppet/modules/release_account/files/chroots/${::osfamily}/chroot-20070718.tar,
checksum = sha256lite,
}
Results in:
Notice: /Stage[main]/Release_account::Redhat::Chroot/File[chroot-20070718.tar]/content: current_value
{sha256lite}3b155333d1cb1ed4e96f791c16dda06d95c47ded1b206240ed61c2c09f1426ba, should be
Jira (PUP-2706) Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Title: Message Title
Kenneth Barber commented on an issue
Re: Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Melissa Stone I just added a blocking link to this ticket to track that.
Add Comment
Puppet / PUP-2706
Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
We keep getting this error during Puppet installation for our PuppetDB builds: {code} Setting up ruby-augeas (0.5.0-2) ... Setting up libaugeas-ruby (0.5.0-2) ... Setting up ruby-shadow (2.2.0-1) ... Setting up ruby-json (1.8.0-1build1) ... Setting up hiera (1.3.3-1puppetlabs1) ... Setting up puppet-common (3.6.1-1puppetlabs1) ... chage: the sha...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3549) Debian init script status and stop actions are unsafe
Title: Message Title
Tomasz Kuzemko commented on an issue
Re: Debian init script status and stop actions are unsafe
Submitted pull request: https://github.com/puppetlabs/puppet/pull/3239
Add Comment
Puppet / PUP-3549
Debian init script status and stop actions are unsafe
Calling {{/etc/init.d/puppet stop}} does not guarantee that the process being stopped is actually puppet agent process. {{start-stop-daemon}} will kill any process which PID happens to be the same as the one stored in {{/var/run/puppet/agent.pid}}. The same applies to {{/etc/init.d/puppet status}}. It calls {{status_of_proc}} internally, but that does ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3546) Modify exec node terminus to support JSON
Title: Message Title
Andy Parker commented on an issue
Re: Modify exec node terminus to support JSON
This one isn't strictly necessary. Since puppet doesn't really produce the YAML, it can also be left as it is.
Add Comment
Puppet / PUP-3546
Modify exec node terminus to support JSON
The exec node terminus currently expects the command is executes to print YAML to stdout. The terminus then parses this and constructs a {{Puppet::Node}} from the data. As part of the switch to JSON, the exec node terminus should extend its protocol to handle JSON. The exec node terminus reads the first line of the commands stdout. The first line *may*...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3524) Switch from YAML and PSON to JSON
Title: Message Title Andy Parker commented on an issue Re: Switch from YAML and PSON to JSON I'm leaving out things like config files that puppet doesn't produce. This means things like the certificate extensions on an agent aren't on this list of items. I did create a ticket for the exec ENC, but it isn't something that really has to be done and we can decide to just close it won't fix with no detriment to other tickets. Add Comment Puppet / PUP-3524 Switch from YAML and PSON to JSON I'd like to move us away from PSON and onto a standard format. YAML is out of the question because it is either slow and unsafe (all of the YAML vulnerabilities) or extremely slow and safe (safe_yaml). MessagePack might be nice. It is pretty well specified, has a fairly large number of libraries written for it, but it doesn't do much to help us solve the ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Andy Parker commented on an issue Re: Facter logs should be surfaced during Puppet runs Shouldn't this be a facter ticket? And then have a ticket for Puppet to use the new facility? Add Comment Puppet / PUP-2927 Facter logs should be surfaced during Puppet runs Information logged by Hiera [is forwarded to Puppet loggers|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/puppet_logger.rb] when Hiera is running as part of a Puppet process. Facter should do the same thing. For Facter, this is especially critical since custom facts contain arbitrary user-written code that can have a variety of side effects... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/142/ Add Comment PuppetDB / PDB-990 PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt h2. Ticket/master/pdb 954 fallback acceptance * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129] * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files] h2. Pull Request Description (webhooks-id... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PDB-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt Pull request Ticket/master/pdb 954 fallback acceptance has been closed. Add Comment PuppetDB / PDB-990 PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt h2. Ticket/master/pdb 954 fallback acceptance * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129] * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files] h2. Pull Request Description (webhooks-id... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-885) PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-885 PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber Change By: Kenneth Barber Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Joshua Partlow commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. Acceptance did not run Sunday, and was aborted, it looks like, last night, but we did get a run through Saturday. Based on that, the sporadic tests/concurrency/ticket_2659_concurrent_catalog_requests.rb appear to have been fixed by the work Dan and Ruth did in PE-6571. All we have left are the very regular woy_cache and selinux failures listed in this comment: Failures on 10/23 Per Wayne's suggestion, I ran some vms Saturday with an auditd trail on /etc/puppetlabs/puppet/ssl, and I believe there is a change to the certs/ca.pem file's ownership in the woy_cache test, but none of my test runs was also obliging me with a failure in that test, and I don't know why the ownership is changing. I still have no idea what's going on with the selinux failures. Add Comment Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Kylo Ginsberg commented on an issue Re: Facter logs should be surfaced during Puppet runs I agree, sounds like this needs a matching facter ticket. Why is this in the 'JSON All the Things!' epic? I'm missing something. Add Comment Puppet / PUP-2927 Facter logs should be surfaced during Puppet runs Information logged by Hiera [is forwarded to Puppet loggers|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/puppet_logger.rb] when Hiera is running as part of a Puppet process. Facter should do the same thing. For Facter, this is especially critical since custom facts contain arbitrary user-written code that can have a variety of side effects... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-998) PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-998 PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior Issue Type: Task Assignee: Unassigned Created: 27/Oct/14 12:43 PM Labels: github Priority: Normal Reporter: gepetto-bot Switching RPM/DEB package to use globbing on terminus directories Author: Ryan Senior senior.r...@gmail.com Company: Github ID: senior Pull Request 1131 Discussion Pull Request 1131 File Diff Pull Request Description (webhooks-id: 0fa8e027e53608cbb647baf657c0861d)
Jira (PDB-998) PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior senior commented: @kbarber @haus Does this look like what we want? Add Comment PuppetDB / PDB-998 PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior h2. Switching RPM/DEB package to use globbing on terminus directories * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 1131 Discussion|https://github.com/puppetlabs/puppetdb/pull/1131] * [Pull Request 1131 File Diff|https://github.com/puppetlabs/puppetdb/pull/1131/files] h2. P... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-3479) Windows ffi dependency fails for Ruby 2.1.3
Title: Message Title Michael Smith commented on an issue Re: Windows ffi dependency fails for Ruby 2.1.3 Hiera had no explicit dependency on ffi. I could add one, but I don't see a reason it's needed. Michael Add Comment Puppet / PUP-3479 Windows ffi dependency fails for Ruby 2.1.3 Ruby 2.1.x was released on Windows for the first time with Ruby 2.1.3 in September: https://www.ruby-forum.com/topic/5768030 Running Ruby from source on Windows with Ruby 2.1.3 fails, because ffi 1.9.3 isn't compatible with Ruby 2.1.x. The ffi dependency needs to be updated to require ffi 1.9.5+ on all our projects that depend on it: at least puppet, f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1208) md5lite, mtime not honoured for file type/provider
Title: Message Title
Eric Sorenson commented on an issue
Re: md5lite, mtime not honoured for file type/provider
Linked
PUP-2976
here to reduce dups.
Add Comment
Puppet / PUP-1208
md5lite, mtime not honoured for file type/provider
It seems I can't get the puppetmaster to honour the checksum = mtime setting, or the md5lite setting. So the following example has no performance improvement over just using md5: {code} file { /testtransfer: ensure = directory, recurse = remote, purge = true, checksum = mtime, source = puppet:///modules/${module_name}/bigfilesh...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-1208) md5lite, mtime not honoured for file type/provider
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-1208 md5lite, mtime not honoured for file type/provider Change By: Eric Sorenson Assignee: CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-998) PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior senior commented: @kbarber @haus ok, let's try this again, pushed an update with the changes Add Comment PuppetDB / PDB-998 PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior h2. Switching RPM/DEB package to use globbing on terminus directories * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 1131 Discussion|https://github.com/puppetlabs/puppetdb/pull/1131] * [Pull Request 1131 File Diff|https://github.com/puppetlabs/puppetdb/pull/1131/files] h2. P... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more
Jira (PUP-3479) Windows ffi dependency fails for Ruby 2.1.3
Title: Message Title Michael Smith commented on PUP-3479 Re: Windows ffi dependency fails for Ruby 2.1.3 Hiera had no explicit dependency on ffi. I could add one, but I don't see a reason it's needed. Michael Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1208) md5lite, mtime not honoured for file type/provider
Title: Message Title
Eric Sorenson commented on an issue
Re: md5lite, mtime not honoured for file type/provider
Check out this one weird old bug, discovered by a sysadmin...
Charlie Sharpsteen can you verify the proposed fix? Seems like a pretty severe thing to have a 1-line fix just sitting around. cc Kylo Ginsberg
Add Comment
Puppet / PUP-1208
md5lite, mtime not honoured for file type/provider
It seems I can't get the puppetmaster to honour the checksum = mtime setting, or the md5lite setting. So the following example has no performance improvement over just using md5: {code} file { /testtransfer: ensure = directory, recurse = remote, purge = true, checksum = mtime, source = puppet:///modules/${module_name}/bigfilesh...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (PDB-998) PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior haus commented: :+1: LGTM Add Comment PuppetDB / PDB-998 PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior h2. Switching RPM/DEB package to use globbing on terminus directories * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 1131 Discussion|https://github.com/puppetlabs/puppetdb/pull/1131] * [Pull Request 1131 File Diff|https://github.com/puppetlabs/puppetdb/pull/1131/files] h2. P... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3479) Windows ffi dependency fails for Ruby 2.1.3
Title: Message Title Rob Reynolds commented on an issue Re: Windows ffi dependency fails for Ruby 2.1.3 Nope, let's not add one. I was just following up on the comment in the description about puppet/facter/hiera. Add Comment Puppet / PUP-3479 Windows ffi dependency fails for Ruby 2.1.3 Ruby 2.1.x was released on Windows for the first time with Ruby 2.1.3 in September: https://www.ruby-forum.com/topic/5768030 Running Ruby from source on Windows with Ruby 2.1.3 fails, because ffi 1.9.3 isn't compatible with Ruby 2.1.x. The ffi dependency needs to be updated to require ffi 1.9.5+ on all our projects that depend on it: at least puppet, f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3512) Add deprecation warning for old profiler API in Puppet
Title: Message Title Christopher Price updated an issue Puppet / PUP-3512 Add deprecation warning for old profiler API in Puppet Change By: Christopher Price Sprint: SERVERnext sprint candidates 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3521) puppet incorrectly swallows some errors
Title: Message Title Christopher Price updated an issue Puppet / PUP-3521 puppet incorrectly swallows some errors Change By: Christopher Price Sprint: SERVERnext sprint candidates 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3519) Scope URL rework
Title: Message Title Christopher Price updated an issue Puppet / PUP-3519 Scope URL rework Change By: Christopher Price Sprint: SERVERnext sprint candidates 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-998) PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior Pull request Switching RPM/DEB package to use globbing on terminus directories has been closed. Add Comment PuppetDB / PDB-998 PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior h2. Switching RPM/DEB package to use globbing on terminus directories * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 1131 Discussion|https://github.com/puppetlabs/puppetdb/pull/1131] * [Pull Request 1131 File Diff|https://github.com/puppetlabs/puppetdb/pull/1131/files] h2. P... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-3520) Move the Puppet extension OIDs definitions
Title: Message Title Christopher Price updated an issue Puppet / PUP-3520 Move the Puppet extension OIDs definitions Change By: Christopher Price Sprint: SERVERnext sprint candidates 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3523) Scope work required to override environment caching behavior
Title: Message Title Christopher Price updated an issue Puppet / PUP-3523 Scope work required to override environment caching behavior Change By: Christopher Price Sprint: SERVERnext sprint candidates 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3479) Windows ffi dependency fails for Ruby 2.1.3
Title: Message Title Michael Smith commented on PUP-3479 Re: Windows ffi dependency fails for Ruby 2.1.3 Hiera had no explicit dependency on ffi. I could add one, but I don't see a reason it's needed. Michael Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3511) Refactor Application.run() logic in core Ruby Puppet for external reuse
Title: Message Title Christopher Price updated an issue Puppet / PUP-3511 Refactor Application.run() logic in core Ruby Puppet for external reuse Change By: Christopher Price Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1208) md5lite, mtime not honoured for file type/provider
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-1208 md5lite, mtime not honoured for file type/provider Change By: Eric Sorenson Component/s: TypesandProviders Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3522) Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module
Title: Message Title Christopher Price updated an issue Puppet / PUP-3522 Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module Change By: Christopher Price Sprint: SERVERnext sprint candidates 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3522) Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module
Title: Message Title Josh Cooper commented on an issue Re: Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module Ideally all networking connections would go through Puppet::Network::HTTP.http_instance so that we can ensure we disable insecure protocols, e.g. SSLv2/3, allow the ciphersuite string to be specified, etc. However, some code paths don't, notably anything using open-uri. As a result, we monkey patch to ensure that doesn't happen. Long term, we should remove usage of open-uri, e.g. PMT, appdmg pkgdmg providers, etc, and then move the monkey patch to our http connection factory. Short term, we might be able to skip the monkey patch when running in JRuby? Add Comment Puppet / PUP-3522 Ruby OpenSSL executed implicitly in JVM-Puppet by loading Puppet/Util module When [~andrew.roetker] first tried to bring up JVM-Puppet on Debian, he encountered an OpenSSL::X509::StoreError -- stack trace below. This happened during initialization of one of the JRuby ScriptingContainers for Ruby Puppet use during launch of the Java process. We have yet to be able to reproduce anything like this when running JVM-Puppet on CentO... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Nicholas Fagerlund commented on an issue Re: Puppet needs to use default keylength 2048 on FIPS enabled systems Kylo Ginsberg The only sufficient docs for this would be just-in-time docs. (Explanation in keylength setting: no one will go looking there. Explanation in install guide: clogs up guide with irrelevant info and degrades experience for all non-FIPS users. Explanation in troubleshooting page where info goes to die: no one will go looking there. Explanation in separate FIPS page: no one will go looking there.) Anyway, when we fail to generate initial certificates due to FIPS being enabled, we should, AT THAT TIME, emit a message explaining what happened and pointing at the keylength setting. What is the current symptom of this failure? We should change that symptom to be explicit and helpful. That's the solution I'd be satisfied with. Add Comment Puppet / PUP-3114 Puppet needs to use default keylength 2048 on FIPS enabled systems FIPS 140-2 does not allow for the use of 4096 bit keys. Therefore, the initial certificate generation of a key using a key length 2048 bits will fail. Any system that is FIPS enabled, should use a 2048 bit key when generating the initial CA and server certificates. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-998) PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/144/ Add Comment PuppetDB / PDB-998 PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior h2. Switching RPM/DEB package to use globbing on terminus directories * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 1131 Discussion|https://github.com/puppetlabs/puppetdb/pull/1131] * [Pull Request 1131 File Diff|https://github.com/puppetlabs/puppetdb/pull/1131/files] h2. P... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PDB-998) PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/143/ Add Comment PuppetDB / PDB-998 PR (1131): Switching RPM/DEB package to use globbing on terminus directories - senior h2. Switching RPM/DEB package to use globbing on terminus directories * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 1131 Discussion|https://github.com/puppetlabs/puppetdb/pull/1131] * [Pull Request 1131 File Diff|https://github.com/puppetlabs/puppetdb/pull/1131/files] h2. P... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Josh Cooper commented on an issue Re: Puppet needs to use default keylength 2048 on FIPS enabled systems OpenSSL will segfault if puppet tries to use a non-FIPS compatible keylength on a FIPS enabled system, which is part of the problem... you can't deploy puppet and then try to use puppet to manage the keylength setting. It has to set correctly to start with... Add Comment Puppet / PUP-3114 Puppet needs to use default keylength 2048 on FIPS enabled systems FIPS 140-2 does not allow for the use of 4096 bit keys. Therefore, the initial certificate generation of a key using a key length 2048 bits will fail. Any system that is FIPS enabled, should use a 2048 bit key when generating the initial CA and server certificates. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more
Jira (PUP-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Trevor Vaughan commented on an issue Re: Puppet needs to use default keylength 2048 on FIPS enabled systems Yeah, this is why I finally decided to patch it instead of a doc update. Add Comment Puppet / PUP-3114 Puppet needs to use default keylength 2048 on FIPS enabled systems FIPS 140-2 does not allow for the use of 4096 bit keys. Therefore, the initial certificate generation of a key using a key length 2048 bits will fail. Any system that is FIPS enabled, should use a 2048 bit key when generating the initial CA and server certificates. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3551) Strip non-UTF-8 data from run reports
Title: Message Title Andy Parker created an issue Puppet / PUP-3551 Strip non-UTF-8 data from run reports Issue Type: Improvement Assignee: Unassigned Created: 27/Oct/14 1:35 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker One of the consequences of using JSON and the existing serialization of reports is that it won't be able to handle non-UTF-8 showing up. Non-UTF-8 data would not show up from the catalog information (since it also has the same UTF-8 restriction), but it can show up in the output of the commands that puppet runs as part of applying a catalog. Puppet must be able to send the report about the run. It can't be stopped by some data that prevents a particular serialization mechanism from working correctly. In order to send the report puppet should strip any non-UTF-8 sequences in the report and replace them with something that can be serialized. Add Comment
Jira (PUP-3551) Strip non-UTF-8 data from run reports
Title: Message Title Andy Parker commented on an issue Re: Strip non-UTF-8 data from run reports Ideally the fact that the agent had to strip some data would be recorded somewhere in the report. Add Comment Puppet / PUP-3551 Strip non-UTF-8 data from run reports One of the consequences of using JSON and the existing serialization of reports is that it won't be able to handle non-UTF-8 showing up. Non-UTF-8 data would not show up from the catalog information (since it also has the same UTF-8 restriction), but it can show up in the output of the commands that puppet runs as part of applying a catalog. Puppet *mu... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Andy Parker commented on an issue Re: Facter logs should be surfaced during Puppet runs I added it to JSON All the Things because I noticed that the message the facter produces when it hits non-UTF-8 facts doesn't go through puppet's logging system, which means that it wouldn't make it into a report. I was thinking that part of making a good user experience for JSON All the Things would be to include logs about when non-UTF-8 data is hit. Can't do this for the master side, but it should be doable for the agent side. Add Comment Puppet / PUP-2927 Facter logs should be surfaced during Puppet runs Information logged by Hiera [is forwarded to Puppet loggers|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/puppet_logger.rb] when Hiera is running as part of a Puppet process. Facter should do the same thing. For Facter, this is especially critical since custom facts contain arbitrary user-written code that can have a variety of side effects... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and
Jira (PUP-3552) Use application/json Content-Type/Accept instead of PSON
Title: Message Title Andy Parker created an issue Puppet / PUP-3552 Use application/json Content-Type/Accept instead of PSON Issue Type: Improvement Assignee: Unassigned Created: 27/Oct/14 1:47 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker Once puppet is handling everything as JSON instead of PSON, we need to change from using application/pson (or variants) to application/json (strictly, don't accept just json or x-json or any other variations). In order to be mostly backwards compatible puppet should still accept PSON content types but only decode and encode them like JSON. When it does this it needs to issue a warning about using a deprecated format and that it is no longer fully functional. Add Comment
Jira (PUP-3433) Remove defunct code from Puppet::Util::Autoload
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-3433 Remove defunct code from Puppet::Util::Autoload Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3516) Puppet breaks on 32-bit Windows XP
Title: Message Title
Josh Cooper commented on an issue
Re: Puppet breaks on 32-bit Windows XP
Specifically, remove the attach_function calls to Wow* functions and the sites where those calls are made. Then modify RegOpenKeyEx call sites, passing in KEY_WOW64_64KEY = 0x100. This will disable registry redirection when running 32-bit apps on 64-bit OS, and will be ignored on 32-bit OS. See http://msdn.microsoft.com/en-us/library/windows/desktop/aa384129(v=vs.85).aspx
Add Comment
Puppet / PUP-3516
Puppet breaks on 32-bit Windows XP
The new win32-eventlog version that Puppet is using is looking for {{Wow64DisableWow64FsRedirection}}. However, that only exists in {{kernel.dll}} on Windows XP 64bit Edition and Vista and upwards. This currently results in Puppet exploding on 'normal' Windows XP: {noformat} C:/Programme/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/ffi-1.9
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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.
Jira (PUP-3553) Remove support for OSX versions = 10.6
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-3553 Remove support for OSX versions = 10.6 Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3553) Remove support for OSX versions = 10.6
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-3553 Remove support for OSX versions = 10.6 Issue Type: Improvement Assignee: Unassigned Created: 27/Oct/14 2:05 PM Priority: Normal Reporter: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3114) Puppet needs to use default keylength 2048 on FIPS enabled systems
Title: Message Title Nicholas Fagerlund commented on an issue Re: Puppet needs to use default keylength 2048 on FIPS enabled systems Does OpenSSL at least crash with an informative message? Can we do anything after OpenSSL crashes and tell the user what might be up? Can we detect what's up before OpenSSL crashes and give a message then? Anyway, my answer about addressing this in docs stands: we can put something on the website and say we technically did something, but we can't put something on the website and say it solves the problem. Users won't know to even check the docs unless they get a clear signal about what just happened to them. Add Comment Puppet / PUP-3114 Puppet needs to use default keylength 2048 on FIPS enabled systems FIPS 140-2 does not allow for the use of 4096 bit keys. Therefore, the initial certificate generation of a key using a key length 2048 bits will fail. Any system that is FIPS enabled, should use a 2048 bit key when generating the initial CA and server certificates. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed
Jira (PUP-3523) Scope work required to override environment caching behavior
Title: Message Title Christopher Price updated an issue Puppet / PUP-3523 Scope work required to override environment caching behavior Change By: Christopher Price Sprint: SERVERnext sprint candidates 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3523) Scope work required to override environment caching behavior
Title: Message Title Christopher Price updated an issue Puppet / PUP-3523 Scope work required to override environment caching behavior Change By: Christopher Price Sprint: SERVER nextsprintcandidates 2014-11-5 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3475) Plan transition to JSON
Title: Message Title Andy Parker commented on an issue Re: Plan transition to JSON Someone please review that the various tickets I've entered in the epic for this covers what will need to be done for transitioning from YAML/PSON to JSON. Add Comment Puppet / PUP-3475 Plan transition to JSON Plan out how we can move from PSON to JSON in all cases where PSON is currently being used. There are backwards compatibility issues that need to be handled for this as well. At the very least we need to be able to provide users of older agents a good way of being told what is happening rather than Can't intern from JSON (or something equally unhelpful)... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3525) Puppetmaster needs a RESTful way to flush environment caches
Title: Message Title Christopher Price updated an issue Puppet / PUP-3525 Puppetmaster needs a RESTful way to flush environment caches Change By: Christopher Price Component/s: PuppetServer Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3533) File resource doesn't handle NTFS junctions well
Title: Message Title
Josh Cooper commented on an issue
Re: File resource doesn't handle NTFS junctions well
Brian Krische if this used to work in versions of puppet prior to 3.6, but doesn't anymore, it may be related to PUP-2788. If it never worked, well that sounds like a different issue.
In either case, can you add the --trace option, rerun the command that fails, and paste the backtrace into this ticket?
Add Comment
Puppet / PUP-3533
File resource doesn't handle NTFS junctions well
Puppet (specifically the file resource) doesn't seem to consistently handle NTFS folder junctions in Windows. Here are some steps to reproduce: # Create a directory and directory junction in Windows #* {{mkdir C:\directory}} #* {{mklink /J C:\junction C:\directory}} # Create a file inside the junction (*this works*) #* {{puppet resource file C:\jun...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-1208) md5lite, mtime not honoured for file type/provider
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1208 md5lite, mtime not honoured for file type/provider Change By: Charlie Sharpsteen Affects Version/s: PUP3.7.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3465) create acceptance test; package creates example environment with readme
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3465 create acceptance test; package creates example environment with readme Change By: Eric Thompson Summary: createacceptancetest;packagecreates default example environmentwith site.pp readme Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3523) Scope work required to override environment caching behavior
Title: Message Title Christopher Price commented on an issue Re: Scope work required to override environment caching behavior Have done a bit of POC'ing and talked this through with Eric Sorenson, and a little with Andy Parker. This is the plan for now: Changes to Puppet to introduce an override-able factory object for creating environment cache entries In Puppet Server, provide an implementation of this factory. The implementation should basically expose a function that can be called to flag all of the environments as stale. Introduce a new 'admin' HTTP API in Puppet Server, with a config setting for whitelisting certificates that should have access to it Add a new endpoint in the 'admin' API called, e.g., flush_environment_cache, which will call the function exposed by the Puppet Server environment cache factory implementation. FUTURE: provide a more general way of configuring authorization for endpoints that are not routed through the current auth.conf plumbing. Creating tickets for the above items now, will link them here when they're finished. Add Comment Puppet / PUP-3523 Scope work required to override environment caching behavior
Jira (PUP-1208) md5lite, mtime not honoured for file type/provider
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1208 md5lite, mtime not honoured for file type/provider Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1208) md5lite, mtime not honoured for file type/provider
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: md5lite, mtime not honoured for file type/provider
Re-produced on 3.7.2 and current master. Ken's patch (provided in description) appears to resolve this, although it needs to be applied to the find method in addition to the search method.
Add Comment
Puppet / PUP-1208
md5lite, mtime not honoured for file type/provider
It seems I can't get the puppetmaster to honour the checksum = mtime setting, or the md5lite setting. So the following example has no performance improvement over just using md5: {code} file { /testtransfer: ensure = directory, recurse = remote, purge = true, checksum = mtime, source = puppet:///modules/${module_name}/bigfilesh...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-1208) md5lite, mtime not honoured for file type/provider
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: md5lite, mtime not honoured for file type/provider
Andy Parker: Looks like a server side issue with a trivial patch, should we target this at stable or 4.0?
Add Comment
Puppet / PUP-1208
md5lite, mtime not honoured for file type/provider
It seems I can't get the puppetmaster to honour the checksum = mtime setting, or the md5lite setting. So the following example has no performance improvement over just using md5: {code} file { /testtransfer: ensure = directory, recurse = remote, purge = true, checksum = mtime, source = puppet:///modules/${module_name}/bigfilesh...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3471 Windows Puppet x86 Installer on x64 system issue For verifying this fix for FR, please see the SavePath.png attached file to add %systemroot\windows32 to the System PATH variable. Change By: Rob Reynolds Attachment: SavePath.png Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-3471) Windows Puppet x86 Installer Expands Path Variables
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3471 Windows Puppet x86 Installer Expands Path Variables Change By: Rob Reynolds Summary: WindowsPuppetx86Installer onx64systemissue ExpandsPathVariables Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3471) Windows Puppet x86 Installer Expands Path Variables
Title: Message Title Rob Reynolds commented on an issue Re: Windows Puppet x86 Installer Expands Path Variables Baptiste Hebert From the looks of things, the removal of the variables entirely is probably something to do with your script and what the current installer is doing to those path variables. Add Comment Puppet / PUP-3471 Windows Puppet x86 Installer Expands Path Variables When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards. In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environments For example, before Puppet installation we had: PATH=%SystemRoot%\system32;%SystemRoot%;%SystemRo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options,
