Jira (PUP-2648) Error On upgrading augeas-libs
Title: Message Title Stephane M created an issue Puppet / PUP-2648 Error On upgrading augeas-libs Issue Type: Bug Affects Versions: 3.6.0 Assignee: Aaron Armstrong Components: PE Created: 23/May/14 12:51 AM Environment: Linux RHEL5/6 Labels: augeas_libs conflicts Priority: Major Reporter: Stephane M Original Estimate: 2 days Remaining Estimate: 2 days
Jira (PDB-686) java.util.concurrent.TimeoutException: Idle timeout expired on Ubuntu 12.04 and Ruby 1.9.3p0 since PDB 2.0.0
Title: Message Title
Jrgen Weber commented on an issue
Re: java.util.concurrent.TimeoutException: Idle timeout expired on Ubuntu 12.04 and Ruby 1.9.3p0 since PDB 2.0.0
Hi, yes. I added the brightbox PPA and it works. Thanks
Add Comment
PuppetDB / PDB-686
java.util.concurrent.TimeoutException: Idle timeout expired on Ubuntu 12.04 and Ruby 1.9.3p0 since PDB 2.0.0
on puppet agent run: {code} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace catalog' command for vagrant-tools01.intfd.local to PuppetDB at vagrant-tools01.intfd.local:8081: [500 java.util.concurrent.TimeoutException: Idle timeout expired: 3/3 ms] htmlheadmeta http-equiv=Content-Type ...
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-1125) Exec checks should be turned into metaparameters
Title: Message Title Frederik Wagner commented on an issue Re: Exec checks should be turned into metaparameters A usecase which I hit multiple times is be for the package type: Install Package A only if Package B ist not installed @John: I agree it's more an imparitive/scriptlike way of using puppet here. Anyway a common usecase (in particular for installation of badly packaged 3rd party vendor software). For now this is easily solved by an exec statement, but then the advantages of the usage of the existing types are lost. Add Comment Puppet / PUP-1125 Exec checks should be turned into metaparameters The 'checks' in Exec -- refreshonly, onlyif and unless -- should be changed into metaparameters, so they're available for all resource types. My guess is that this will require defining a new type of metaparameter, in the same way that the Exec checks are a slightly different type of parameter. 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,
Jira (PUP-2635) user purge_ssh_keys not purged
Title: Message Title
Felix Frank commented on an issue
Re: user purge_ssh_keys not purged
Doug Byrne, can you plase share the contents of ~ubuntu/.ssh/authorized_keys?
This may be a bug in the parsing of keys for purging, which unfortunately cannot rely on the actual auth-key type/provider code.
Add Comment
Puppet / PUP-2635
user purge_ssh_keys not purged
I'm using Puppet 3.6.0 on Ubuntu 12.04 and I'm trying to purge unmanaged ssh authorized keys. I've added this code to my manifest: {code} user { 'ubuntu': purge_ssh_keys = true, home = '/home/ubuntu', } {code} However, no keys are purged. I do see the following lines in the agent debug output: {noformat} Debug: /Stage[main]/Role...
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-2649) hiera_include with Puppet 3.5
Title: Message Title
adrian created an issue
Puppet / PUP-2649
hiera_include with Puppet 3.5
Issue Type:
Bug
Affects Versions:
3.6.1, 3.6.0, 3.5.1, 3.5.0
Assignee:
Andy Parker
Components:
DSL
Created:
23/May/14 2:36 AM
Priority:
Normal
Reporter:
adrian
With Puppet 3.5 comes deprecation of import (http://docs.puppetlabs.com/puppet/latest/reference/lang_import.html), so all node definitions should be in different files each of one should begin with node ..., it is correct?
Which is the correct way to use hiera_include in Puppet 3.5+? Because in the doc (http://docs.puppetlabs.com/hiera/1/puppet.html#assigning-classes-to-nodes-with-hiera-hierainclude) it says In your main manifest, write the line hiera_include('classes'). Put this outside any node definition.
Add Comment
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Paul Seymour created an issue Puppet / PUP-2650 3.6.1 issues warning message for deprecation Issue Type: Bug Affects Versions: 3.6.1 Assignee: Unassigned Created: 23/May/14 2:57 AM Priority: Normal Reporter: Paul Seymour Message is issued from agent runs at the warning level for a deprecation message. Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false. (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in `set_default') Add Comment
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Dominic Cleal commented on an issue Re: 3.6.1 issues warning message for deprecation While I appreciate the changes to virtual packages noted in the release notes are slightly complex, this warning (any time a package + yum resource is used) probably isn't necessary for most users. It seems to me that virtual package support is regarded as a positive change in the upcoming Puppet 4, so I don't think a warning on each run is needed to inform users that they might be missing out on it. I'd ask for the log level to be changed to info or notice, or for the deprecation warning to be removed entirely. I think the release notes are clear and probably sufficient: http://docs.puppetlabs.com/puppet/latest/reference/release_notes.html#changes-to-rpm-behavior-with-virtual-packages. I'm unsure that users should have to follow the recommendation to set a system-wide default for allow_virtual to quieten this message. Add Comment Puppet / PUP-2650 3.6.1 issues warning message for deprecation Message is issued from agent runs at the warning level for a deprecation message. Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false. (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (HI-257) Dynamic hierarchy based on fact/variable
Title: Message Title
Matteo Cerutti created an issue
Hiera / HI-257
Dynamic hierarchy based on fact/variable
Issue Type:
New Feature
Assignee:
Unassigned
Created:
23/May/14 3:25 AM
Priority:
Normal
Reporter:
Matteo Cerutti
Take the following hierarchy example:
hiera/%{::variable}/common
let's say $variable is an array: $variable = [a, b, c]
Hiera understands that $variable is an array and it would then build an hierarchy as follows:
hiera/a/common
hiera/b/common
hiera/c/common
Both these examples find real work scenarios. Let's say a machine as a number of roles (webserver, dns server etc.). One could have an array containing each role and build the hierarchy based on that. Extremely powerful.
Jira (PUP-2651) Loading facts happens twice when environmentpath is in then main section of puppet.conf
Title: Message Title Stefan Heijmans created an issue Puppet / PUP-2651 Loading facts happens twice when environmentpath is in then main section of puppet.conf Issue Type: Bug Affects Versions: 3.6.1 Assignee: Eric Sorenson Components: Community Created: 23/May/14 3:50 AM Environment: VMware guest with RHEL6.5 Ruby 1.8.7.352-13 Puppet 3.6.1 Priority: Normal Reporter: Stefan Heijmans Did an upgrade from Puppet 3.4.3 to 3.6.1 (and also 3.6.0). Now with a puppet run on the puppet master, facts are loaded twice, from modules directory and /var/lib/puppet; Info: Retrieving plugin Info: Loading facts in /etc/puppet/environments/tst/modules/netbackup/lib/facter/netbackup_agent_version.rb Info: Loading facts in /etc/puppet/environments/tst/modules/netbackup/lib/facter/netbackup.rb Info: Loading facts in /etc/puppet/environments/tst/modules/multipath/lib/facter/lvm2version.rb Info: Loading facts in /etc/puppet/environments/tst/modules/multipath/lib/facter/multipathversion.rb Info: Loading facts in /etc/puppet/environments/tst/modules/common/lib/facter/vendor.rb Info: Loading facts in
Jira (PUP-1035) Default setting for pluginsource problematic for deployments using SRV records
Title: Message Title Michael Drzal commented on an issue Re: Default setting for pluginsource problematic for deployments using SRV records This actually seems to be partially an interaction with facter. facter-1.7.5 works fine. facter-2.* gives this error. Add Comment Puppet / PUP-1035 Default setting for pluginsource problematic for deployments using SRV records The current default for the `pluginsource` setting is `puppet://$server/plugins`. This works well with a `server` set, but in deployments that utilize 3.0's SRV record feature, the `server` setting is likely not utilized at all for communication with a master, and will often be unset. If SRV records are in use the `pluginsource` still gets filled in w... 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-2635) user purge_ssh_keys not purged
Title: Message Title Doug Byrne commented on an issue Re: user purge_ssh_keys not purged I created a new host for investigation of this issue. Below is the authorized_keys file: # HEADER: This file was autogenerated at Fri May 23 11:34:50 + 2014 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. ssh-rsa B3NzaC1yc2EDAQABAAABAQCpIyCCUkkW4CancW11RlGGmcHyIFtwsgIMQGAdBe3WCc+W9MtZDFEFi3XdHQnSRpbsUuiKhiUIKQfuTWXueWIPxtG+Ujde7Ch5MYPbRZ9MDzSYz2MU8/Ir/y7vNLZBadAR131Ok35qL12TMI0Hpzu2o9Y5ZMaf0uoApZAlotJgSsmFAJyq3rdIeIIpdEvTa3C8Yk9ng1p9Dv3nHdx/SpomFIO7rIKIp/vnxplDMBzU7c3akmbI5G3adcRVbZaxiBgJ4X5OKancyq25jqQtduQmgmDOsyr9+DbhcuUafmHpk/lLQ9c8VgvyqbJBaJ7N45NlBGkaZy/frdSeJ+HSEXTr foreman-122dc11d6-bd1e-43e7-a00d-f8e2d0af54ea ssh-rsa B3NzaC1yc2EDAQABAAABAQC81jWIxrZpzL+IFE9S4yJNMrANeOJke0CbFmk8pBz4rI8RZ+1JBZdD5aZnO15nLVYZlQq1D8BLHy3F02EhfmQBINHUPA373SUedEUPqByQBOslp11sK/u0Op0X7hhW902hOFRszb9VODJifWnkB2bj4FDED6zQf8cIeTIO15CyYxPPeT/EBZ9G4RJsAItXf2ktwWaO94FGcnNYMUzvpsJCMwI4XY8ArqQBsRSrGnauhBD3e1MuqnLF4ujOqLYBwfZ5gw5VSar5i/oSsGswgwjKxmuO0hfTxDVROoIn24AHSTm38lF34djEWIASELEWxDjnFDamawfU2Dpm2MK90Jk/ doug The formeman key should be purged, but: Debug: /Stage[main]/Role::Keytest/Ssh_authorized_key[foreman-122dc11d6-bd1e-43e7-a00d-f8e2d0af54ea]: Nothing to manage: no ensure and the resource doesn't exist Add Comment Puppet / PUP-2635 user purge_ssh_keys not purged I'm using Puppet 3.6.0 on Ubuntu 12.04 and I'm trying to purge unmanaged ssh
Jira (PUP-2649) hiera_include with Puppet 3.5
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2649 hiera_include with Puppet 3.5 Change By: Henrik Lindberg Affects Version/s: 3.6.1 Affects Version/s: 3.6.0 Affects Version/s: 3.5.1 Affects Version/s: 3.5.0 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-2649) hiera_include with Puppet 3.5
Title: Message Title Henrik Lindberg commented on an issue Re: hiera_include with Puppet 3.5 I am sorry, but this is not an appropriate use of a bug report. Please use the appropriate support channels for Puppet to ask questions if you do not find what you are looking for in the available documentation (which I think explains both of your questions). In short. 1. no, you can name the files any way you like, they are processed in alphanumerical order. Feel free to call them nodes_01.pp, nodes_02.pp, or a.pp, b.pp or whatever scheme you like that makes you happy. If you think documentation could explain this better, please file an issue against the relevant section in the documentation. 2. there are no general changes related to how to use hiera specific to 3.5.1. Your question is simply too big to answer this way, please use the user group and/or IRC channel to get help, find examples etc. Add Comment Puppet / PUP-2649 hiera_include with Puppet 3.5 With Puppet 3.5 comes deprecation of import (http://docs.puppetlabs.com/puppet/latest/reference/lang_import.html), so all node definitions should be in different files each of one should begin with node ..., it is correct? Which is the correct way to use hiera_include in Puppet 3.5+? Because in the doc (http://docs.puppetlabs.com/hiera/1/puppet.html... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Chuck Schweizer commented on an issue Re: 3.6.1 issues warning message for deprecation Also setting allow_virtual = true only works if all of your Puppet Masters and Agent are at least 3.6.1. It would be very nice if there wasn't a warning on this message. Add Comment Puppet / PUP-2650 3.6.1 issues warning message for deprecation Message is issued from agent runs at the warning level for a deprecation message. Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false. (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in... 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-2531) Provide validation tool for EPP
Title: Message Title
Henrik Lindberg commented on an issue
Re: Provide validation tool for EPP
On second thought, validate does not need values, it does not check if variables exist - it simply parses in EPP mode and performs validation of the logic. It would be great to add validate in Puppet 4.0, and render during 4.x
Add Comment
Puppet / PUP-2531
Provide validation tool for EPP
For {{.pp}} files users have {{puppet parser validate}} to check if the syntax is right. However, for EPP there is no equivalent command. There needs to be one. If it is possible to accurately detect the file type maybe {{puppet parser validate}} could do the determination automagically. If there isn't, then we could maybe add a flag to the command to ...
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,
Jira (PUP-2531) Provide validation tool for EPP
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2531 Provide validation tool for EPP Change By: Henrik Lindberg Fix Version/s: 4.0.0 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-2652) Handling two depending file resources with recurse
Title: Message Title
Dawid Rabiega created an issue
Puppet / PUP-2652
Handling two depending file resources with recurse
Issue Type:
Bug
Assignee:
Unassigned
Created:
23/May/14 5:45 AM
Priority:
Normal
Reporter:
Dawid Rabiega
There is problem when two file resources depending each other, and one is recurse = true. Following error occurs:
Test case:
$ find . -type f
./modules/test/manifests/init.pp
./modules/test/files/b/x
./modules/test/files/b/z
./modules/test/files/b/y
./manifests/site.pp
./test.pp
$ cat manifests/site.pp
## site.pp
node default {
include test
}
$ cat modules/test/manifests/init.pp
## init.pp
class test {
file { 'dir1':
ensure = absent,
path= '/tmp/a',
before = File['dir2'],
}
file { 'dir2':
ensure = absent,
path= '/tmp/a/b',
source = 'puppet:///modules/test/b',
force = true,
purge = true,
recurse = true,
}
}
$ puppet apply --modulepath ./modules manifests/site.pp
Notice: Compiled catalog for localhost in environment production in 0.11 seconds
Error: Could not set 'file' on ensure: cannot generate tempfile `/tmp/a/b/z20140523-14751-1qpqnds-9'
Error: Could not set 'file' on ensure: cannot generate tempfile `/tmp/a/b/z20140523-14751-1qpqnds-9'
Wrapped exception:
cannot generate tempfile `/tmp/a/b/z20140523-14751-1qpqnds-9'
Error: /Stage[main]/Test/File[/tmp/a/b/z]/ensure: change from absent to file failed: Could not set 'file' on ensure: cannot generate tempfile `/tmp/a/b/z20140523-14751-1qpqnds-9'
Error: Could not set 'file' on ensure: cannot generate tempfile `/tmp/a/b/y20140523-14751-1bxpkko-9'
Error: Could not set 'file' on ensure: cannot generate tempfile `/tmp/a/b/y20140523-14751-1bxpkko-9'
Wrapped exception:
cannot generate tempfile `/tmp/a/b/y20140523-14751-1bxpkko-9'
Error: /Stage[main]/Test/File[/tmp/a/b/y]/ensure: change from absent to
Jira (PUP-2514) Remove support to search for Type in String
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2514 Remove support to search for Type in String Change By: Henrik Lindberg Sprint: Week2014-5-28to2014-6-4 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-2651) Loading facts happens twice when environmentpath is in then main section of puppet.conf
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2651 Loading facts happens twice when environmentpath is in then main section of puppet.conf Change By: Henrik Lindberg Component/s: Community 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-2651) Loading facts happens twice when environmentpath is in then main section of puppet.conf
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2651 Loading facts happens twice when environmentpath is in then main section of puppet.conf Change By: Henrik Lindberg Assignee: EricSorenson 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 (PDB-688) java.lang.OutOfMemoryError
Title: Message Title Kenneth Barber commented on an issue Re: java.lang.OutOfMemoryError jon yeargers the ram utilisation of PDB is an interesting topic. Basically most of the RAM usage is spent processing catalogs, so often it doesn't matter how many nodes you have - 1 big catalogue can push the max requirement up. Its less than ideal, and we'd like to stream this one day somehow, but alas for now thats how it works. I'd recommend 512, then stepping up in similar increments until you don't have a crash. If you get to 2 GB and it still crashes, we might need to look into it. 512-1024 should be enough though. Add Comment PuppetDB / PDB-688 java.lang.OutOfMemoryError Upgraded to v 2.0 via 'yum update'. Restarted puppetdb via 'service puppetdb start' Let clients connect. Wait a day. Notice that puppetdb isn't running any more. Look at /var/log/puppetdb/puppetdb-daemon.log See messages like: Java.lang.OutOfMemoryError: Java heap space Dumping heap to 'file name' Heap dump created [large number in 2.5 sec... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you
Jira (PUP-838) FFI Puppet::Util::Windows::Process module
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-838 FFI Puppet::Util::Windows::Process module Change By: Rob Reynolds Assignee: EthanBrown RobReynolds 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-838) FFI Puppet::Util::Windows::Process module
Title: Message Title Rob Reynolds commented on an issue Re: FFI Puppet::Util::Windows::Process module Looks like there is some more work to do here. Add Comment Puppet / PUP-838 FFI Puppet::Util::Windows::Process module This code was already FFI'ed awhile ago, but there are refactors remaining, such as relying on common DWORD definitions, and function declarations, e.g. CloseHandle. 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-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Aaron Zauner commented on an issue Re: 3.6.1 issues warning message for deprecation what's the reasoning behind this being a warning message? thanks. Add Comment Puppet / PUP-2650 3.6.1 issues warning message for deprecation Message is issued from agent runs at the warning level for a deprecation message. Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false. (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in... 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-2652) Handling two depending file resources with recurse
Title: Message Title
Dawid Rabiega commented on an issue
Re: Handling two depending file resources with recurse
I'm trying to get this working:
## init.pp
class test {
$is_master = false
if $is_master {
$file_ensure = present
$directory_ensure = directory
} else {
$file_ensure = absent
$directory_ensure = absent
}
file { 'dir1':
ensure = $directory_ensure,
path = '/tmp/a',
before = File['dir2'],
}
file { 'dir2':
ensure = $directory_ensure,
path = '/tmp/a/b',
source = 'puppet:///modules/test/b',
force = true,
purge = true,
recurse = true,
}
}
Add Comment
Puppet / PUP-2652
Handling two depending file resources with recurse
There is problem when two file resources depending each other, and one is recurse = true. Following error occurs: Test case: {code} $ find . -type f ./modules/test/manifests/init.pp ./modules/test/files/b/x ./modules/test/files/b/z ./modules/test/files/b/y ./manifests/site.pp ./test.pp $ cat manifests/site.pp ## site.pp node default { ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1125) Exec checks should be turned into metaparameters
Title: Message Title John Bollinger commented on an issue Re: Exec checks should be turned into metaparameters A usecase which I hit multiple times is be for the package type: Install Package A only if Package B ist not installed The Puppet operational model is Puppet evaluates the current state of the machine, it uses that and other information to construct a catalog describing the desired target state, and then it attempts to put the machine into the chosen state. If, as in the case presented, the desired target state depends on whether a given package is installed, then the model demands that that information should be fed in up front (via a custom fact). Often an even better solution is to put the uncertain piece of state – e.g. whether Package B is installed – under management. That is, the best policy with Puppet is frequently tell; don't ask. Particular circumstances may admit other alternatives. Add Comment Puppet / PUP-1125 Exec checks should be turned into metaparameters The 'checks' in Exec -- refreshonly, onlyif and unless -- should be changed into metaparameters, so they're available for all resource types. My guess is that this will require defining a new type of metaparameter, in the same way that the Exec checks are a slightly
Jira (PUP-1125) Exec checks should be turned into metaparameters
Title: Message Title Felix Frank commented on an issue Re: Exec checks should be turned into metaparameters I concur that the feature will not cater to the Puppet model in a strictly constructive fashion. Yes, the current canonical way to solve the described use case are facts. That can become unwieldy if it affects lots of resources, though. (Facter 2 and structured data may mitigate this somewhat). On the other hand, the feature would merely introduce yet another means of controlling when a resource is viable for management. Other such means currently include schedules and the noop metaparameter. From a design perspective, it may at least be interesting to explore the new alleys that such an addition would open up. Good point about possible confusion if the parameters would behave differently than those for exec. Of course, we need not make those parameters into the metaparameters, but invent new ones such as sync_if and ignore_if (if that's the semantics we go for). Add Comment Puppet / PUP-1125 Exec checks should be turned into metaparameters The 'checks' in Exec -- refreshonly, onlyif and unless -- should be changed into metaparameters, so they're available for all resource types. My guess is that this will require defining a new type of metaparameter, in the same way that the Exec checks are a slightly different type of parameter. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-688) java.lang.OutOfMemoryError
Title: Message Title jon yeargers commented on an issue Re: java.lang.OutOfMemoryError Changed to 512M and restarted. Will wait and see how it goes. Add Comment PuppetDB / PDB-688 java.lang.OutOfMemoryError Upgraded to v 2.0 via 'yum update'. Restarted puppetdb via 'service puppetdb start' Let clients connect. Wait a day. Notice that puppetdb isn't running any more. Look at /var/log/puppetdb/puppetdb-daemon.log See messages like: Java.lang.OutOfMemoryError: Java heap space Dumping heap to 'file name' Heap dump created [large number in 2.5 sec... 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-2646) Option to compress / limit /var/lib/puppetdb/reports
Title: Message Title jon yeargers updated an issue Puppet / PUP-2646 Option to compress / limit /var/lib/puppetdb/reports Change By: jon yeargers Forsitesthatdon'thavethewherewithalorresourcestoaddapostgresmachine-itwouldbenicetobeabletocompressallthe.yamlfilesstoredin/var/lib/ puppetdb puppet /reports.Ihave~60clients.Havebeenaddingsteadilyforseveralmonths.Myfolderhas113K.yamlfiles.Maybeanoptionto.GZthefilesastheyareadded.Orexpire/removethemafteracertainperiodoftime..oradifferentialstorageofsortstocompresstheolderones..Justthinkingoutloud. 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-686) java.util.concurrent.TimeoutException: Idle timeout expired on Ubuntu 12.04 and Ruby 1.9.3p0 since PDB 2.0.0
Title: Message Title
Kenneth Barber updated an issue
PuppetDB / PDB-686
java.util.concurrent.TimeoutException: Idle timeout expired on Ubuntu 12.04 and Ruby 1.9.3p0 since PDB 2.0.0
Change By:
Kenneth Barber
onpuppetagentrun:{code}Error:Couldnotretrievecatalogfromremoteserver:Error400onSERVER:Failedtosubmit'replacecatalog'commandforvagrant-tools01.intfd.localtoPuppetDBatvagrant-tools01.intfd.local:8081:[500java.util.concurrent.TimeoutException:Idletimeoutexpired:3/3ms]htmlheadmetahttp-equiv=Content-Typecontent=text/html;charset=ISO-8859-1/titleError500/title/headbodyh2HTTPERROR:500/h2pProblemaccessing/v3/commands.Reason:prejava.util.concurrent.TimeoutException:Idletimeoutexpired:3/3ms/pre/phr/ismallPoweredbyJetty:///small/i/body/html{code} Forumdiscussionhere:https://groups.google.com/forum/#!msg/puppet-users/ktJWWqtmen0/eaLyAG0o2VoJ
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-686) java.util.concurrent.TimeoutException: Idle timeout expired on Ubuntu 12.04 and Ruby 1.9.3p0 since PDB 2.0.0
Title: Message Title Kenneth Barber assigned an issue to Unassigned PuppetDB / PDB-686 java.util.concurrent.TimeoutException: Idle timeout expired on Ubuntu 12.04 and Ruby 1.9.3p0 since PDB 2.0.0 Change By: Kenneth Barber Assignee: KennethBarber 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-1125) Exec checks should be turned into metaparameters
Title: Message Title John Bollinger commented on an issue Re: Exec checks should be turned into metaparameters Yes, the current canonical way to solve the described use case are facts. That can become unwieldy if it affects lots of resources, though. (Facter 2 and structured data may mitigate this somewhat). A site with many such resources therein has bigger problems with its approach. I am not averse to Puppet implicitly channeling people toward practices that will ultimately be more effective for them. On the other hand, the feature would merely introduce yet another means of controlling when a resource is viable for management. Other such means currently include schedules and the noop metaparameter. Perhaps so, and on that basis I could perhaps accept the feature without too much complaint. But I don't think it adequately addresses the alternative package use case. Problems arise when other resources need to depend on one or both of the alternatives, for surely if Package A is not in sync and is prevented from being synchronized by a noop_if parameter, then resources that depend on it must not be synchronized either. What's really wanted for this case is a higher-level abstraction over the pair of packages as alternatives for each other. That would be a lot clearer, and, where appropriate, relationships could then be directed at the pair instead of at one or the other. In some specific Package cases, that can now be done with the new support for virtual packages. For other cases, I think I would be a lot happier with a generic way to express such alternative groups in the DSL than with a way to cobble them together implicitly at catalog application time. Add Comment Puppet / PUP-1125 Exec checks should be turned into metaparameters
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Rudy McComb commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log upgraded to Puppet 3.6.0 issue still exists: Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log 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-690) PR (974): Typo in v4/reports.markdown - kbarber
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-690 PR (974): Typo in v4/reports.markdown - kbarber Issue Type: Task Assignee: Unassigned Created: 23/May/14 9:08 AM Labels: github Priority: Normal Reporter: gepetto-bot Typo in v4/reports.markdown Author: Ken Barber k...@bob.sh Company: Puppet Labs Inc. Github ID: kbarber Pull Request 974 Discussion Pull Request 974 File Diff Pull Request Description The alias for the link to the statuses page was incorrect. Fixed. Signed-off-by: Ken Barber k...@bob.sh (webhooks-id: e0d6450bba6196bc5def26a46a0fdac2)
Jira (PUP-2654) label provider for class/define should capitalize all segments
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2654 label provider for class/define should capitalize all segments Issue Type: Bug Assignee: Unassigned Created: 23/May/14 9:13 AM Fix Versions: 3.7.0 Priority: Normal Reporter: Henrik Lindberg When the label provider produces a label for a define/class etc. all segments of the name should be capitalized. The label is shown in error messages. Reproduce by defining a resource type, and set its title to numeric. The reported name should have all segments capitalized. Add Comment
Jira (PUP-2653) manifest ordering changes order with directory file types that recurse
Title: Message Title
Tony Vu created an issue
Puppet / PUP-2653
manifest ordering changes order with directory file types that recurse
Issue Type:
Bug
Affects Versions:
3.6.1
Assignee:
Unassigned
Created:
23/May/14 9:12 AM
Environment:
all linux
Priority:
Normal
Reporter:
Tony Vu
Manifest ordering produces some unexpected results when a file type is set to directory and recurse.
Steps to reproduce:
1. Create the following manifest on the system under test.
class change_detection {
exec { 'env':
command = /var/tmp/scripts/test.sh,
user = 'root',
require = File['/var/tmp/scripts/'],
}
file { '/var/tmp/scripts/':
ensure = directory,
recurse = true,
source = /etc/puppetlabs/puppet/modules/mymodule/scripts/,
}
}
include change_detection
ordering=title-hash always produces a run in this order:
Notice:
Jira (PDB-685) PR (128): add parameter 'max_threads' to define value in jetty.ini - mklette
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-685 PR (128): add parameter 'max_threads' to define value in jetty.ini - mklette Change By: Kenneth Barber Sprint: 20140521to20140604 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-690) PR (974): Typo in v4/reports.markdown - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-690 PR (974): Typo in v4/reports.markdown - kbarber Change By: Kenneth Barber Sprint: 20140521to20140604 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-685) PR (128): add parameter 'max_threads' to define value in jetty.ini - mklette
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-685 PR (128): add parameter 'max_threads' to define value in jetty.ini - mklette Change By: Kenneth Barber Sprint: 20140521to 20140604 to20140618 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-690) PR (974): Typo in v4/reports.markdown - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-690 PR (974): Typo in v4/reports.markdown - kbarber Change By: Kenneth Barber Story Points: 0 Affects Version/s: 2.1.0 Fix Version/s: 2.1.0 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-690) PR (974): Typo in v4/reports.markdown - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (974): Typo in v4/reports.markdown - kbarber Pull request Typo in v4/reports.markdown has been closed. Add Comment PuppetDB / PDB-690 PR (974): Typo in v4/reports.markdown - kbarber h2. Typo in v4/reports.markdown * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 974 Discussion|https://github.com/puppetlabs/puppetdb/pull/974] * [Pull Request 974 File Diff|https://github.com/puppetlabs/puppetdb/pull/974/files] h2. Pull Request Description The al... 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-2642) selector expression default should be matched last
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2642 selector _expression_ default should be matched last Change By: Joshua Partlow Sprint: Week2014-5- 28 21 to2014- 6 5 - 4 28 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-2589) Puppet 3.6.1 2014-05-23 Release
Title: Message Title Peter Huene updated an issue Puppet / PUP-2589 Puppet 3.6.1 2014-05-23 Release Change By: Peter Huene Assignee: ReleaseEngineering 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-1597) contain cannot contain a fully qualified class
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-1597 contain cannot contain a fully qualified class Change By: Joshua Partlow Sprint: Week2014-4-30to2014-5-7,Week2014-5-7to2014-5-14,Week2014-5- 28 21 to2014- 6 5 - 4 28 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-1028) Test future evaluator impl of Node Expresson
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-1028 Test future evaluator impl of Node Expresson Change By: Joshua Partlow Sprint: Week2014-4-30to2014-5-7,Week2014-5-7to2014-5-14,Week2014-5- 28 21 to2014- 6 5 - 4 28 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-2589) Puppet 3.6.1 2014-05-23 Release
Title: Message Title Peter Huene updated an issue Puppet / PUP-2589 Puppet 3.6.1 2014-05-23 Release Change By: Peter Huene Assignee: ReleaseEngineering 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-2287) Lambda with default valued parameter cannot be overridden
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2287 Lambda with default valued parameter cannot be overridden Change By: Joshua Partlow Sprint: Week2014-4-30to2014-5-7,Week2014-5-7to2014-5-14,Week2014-5- 28 21 to2014- 6 5 - 4 28 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-2642) selector expression default should be matched last
Title: Message Title Joshua Partlow commented on an issue Re: selector _expression_ default should be matched last Merged to master in da289b1 Add Comment Puppet / PUP-2642 selector _expression_ default should be matched last The future evaluator treats a default in a selector _expression_ just like any other value (historically puppet regular did this too - although I may be wrong). It should instead defer matching against a default until no other entry matched (just like the case _expression_ does). This will bite all users that have not followed the advice to place the defau... 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-514) Add optional type to parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-514 Add optional type to parameters Change By: Henrik Lindberg Sprint: Week2014-5- 28 21 to2014- 6 5 - 4 28 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 (FACT-483) Explore extracting FACT-185 fix for use in 1.7.x
Title: Message Title Kylo Ginsberg commented on an issue Re: Explore extracting FACT-185 fix for use in 1.7.x Eric Sorenson is there a PE ticket for this? I'm not clear what PE release this is being requested for. Add Comment Facter / FACT-483 Explore extracting FACT-185 fix for use in 1.7.x There have been a number of customer requests for the EC2 VPC fixes that are in Facter 2. Since PE will be on 1.7.x for a while longer, it'd be nice to make these changes available in a way that customers can make use of. 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-2598) Smoke test packages
Title: Message Title Rob Reynolds commented on an issue Re: Smoke test packages For next time, I improved the command that makes these calls - https://github.com/ferventcoder/vagrant-windows-puppet/blob/master/boxes/smoketest-puppet/shell/windows/SmokeCommands.ps1 Add Comment Puppet / PUP-2598 Smoke test packages Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). If this is a final release then the previous RC (which should be identical to what is currently being released) will have gone through th... 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-690) PR (974): Typo in v4/reports.markdown - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (974): Typo in v4/reports.markdown - kbarber pljenkinsro commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/441/ Add Comment PuppetDB / PDB-690 PR (974): Typo in v4/reports.markdown - kbarber h2. Typo in v4/reports.markdown * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 974 Discussion|https://github.com/puppetlabs/puppetdb/pull/974] * [Pull Request 974 File Diff|https://github.com/puppetlabs/puppetdb/pull/974/files] h2. Pull Request Description The al... 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
Jira (PUP-2633) Bump Gemfile dependency for Puppet to use Facter 2
Title: Message Title Ethan Brown commented on an issue Re: Bump Gemfile dependency for Puppet to use Facter 2 I don't believe this should be closed. Fresh install of bundle from Puppet source on Windows: C:\source\puppet [master +3 ~0 -0 !] git show head commit da289b16c0ac6cfacff8e93c5150c291a784e21b Merge: bd7a103 fa796c9 Author: Josh Partlow jpart...@glatisant.org Date: Fri May 23 09:49:57 2014 -0700 Merge pull request #2687 from hlindberg/PUP-2642_selector-default-out-of-band (PUP-2642) Make default in selector be out of band, raise error nomatch C:\source\puppet [master +3 ~0 -0 !] bundle install --path .bundle/gems Fetching gem metadata from https://rubygems.org/. Fetching gem metadata from https://rubygems.org/.. Resolving dependencies... Installing rake (10.1.1) Installing i18n (0.6.9) Installing multi_json (1.10.1) Installing activesupport (3.2.18) Installing builder (3.0.4) Installing activemodel (3.2.18) Installing arel (3.0.3) Installing tzinfo (0.3.39) Installing activerecord (3.2.18) Installing debug_inspector (0.0.2) Installing binding_of_caller (0.7.2) Installing coderay (1.1.0) Installing columnize (0.8.9) Installing mime-types (1.25.1) Installing rest-client (1.6.7) Installing couchrest (1.2.0) Installing debugger-linecache (1.2.0) Installing debugger-ruby_core_source (1.3.5) Installing debugger (1.6.6) Installing diff-lcs (1.1.3) Installing facter (1.7.5) Installing ffi (1.9.0) Installing rspec-core (2.11.1) Installing rspec-expectations (2.11.3) Installing rspec-mocks (2.11.3) Installing rspec (2.11.0) Installing rspec-instafail (0.2.4) Installing ruby-progressbar (1.5.1) Installing fuubar (1.2.1) Installing json_pure (1.8.1) Installing hiera (1.3.2) Installing metaclass (0.0.4) Installing method_source (0.8.2) Installing minitar (0.5.4) Installing mocha (0.10.5) Installing msgpack (0.5.8) Installing net-ssh (2.9.1) Installing slop (3.5.0) Installing win32console (1.3.2) Installing pry (0.9.12.6) Installing pry-debugger (0.2.2) Installing pry-stack_explorer (0.4.9.1) Using puppet (3.6.1) from source at . Installing rspec-puppet (1.0.1) Installing puppetlabs_spec_helper (0.4.1) Installing rack (1.5.2) Installing rgen (0.6.5) Installing ruby-prof (0.15.1) Installing sqlite3 (1.3.9) Installing stomp (1.3.2) Installing win32-api (1.4.8) Installing windows-api (0.4.2) Installing windows-pr (1.2.3) Installing win32-security (0.1.4) Installing sys-admin (1.5.6) Installing win32-dir (0.4.8) Installing win32-eventlog (0.5.3) Installing win32-process (0.6.6) Installing win32-service (0.7.2) Installing win32-taskscheduler (0.2.2) Installing yarjuf (1.0.5) Using bundler (1.3.5) Your bundle is complete! It was installed into ./.bundle/gems C:\source\puppet [master +3 ~0 -0 !] bundle exec facter --version 1.7.5 Add Comment
Jira (PUP-2633) Bump Gemfile dependency for Puppet to use Facter 2
Title: Message Title Adrien Thebo commented on an issue Re: Bump Gemfile dependency for Puppet to use Facter 2 Ethan Brown and this was with the Gemfile.lock blown away? Add Comment Puppet / PUP-2633 Bump Gemfile dependency for Puppet to use Facter 2 The impetus is that when developing against source, it will by default grab an older than 2.x version of Facter. As developers, we want a newer version. We currently expect 1.6 in the Gemfile, but should probably use a newer 2.x+ version by default https://github.com/puppetlabs/puppet/blob/master/Gemfile#L27 Similarly, we added 1.7+ support, but... 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-2633) Bump Gemfile dependency for Puppet to use Facter 2
Title: Message Title Ethan Brown commented on an issue Re: Bump Gemfile dependency for Puppet to use Facter 2 Haha, I was just checking that out, because I realized I was being stupid. Add Comment Puppet / PUP-2633 Bump Gemfile dependency for Puppet to use Facter 2 The impetus is that when developing against source, it will by default grab an older than 2.x version of Facter. As developers, we want a newer version. We currently expect 1.6 in the Gemfile, but should probably use a newer 2.x+ version by default https://github.com/puppetlabs/puppet/blob/master/Gemfile#L27 Similarly, we added 1.7+ support, but... 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-838) FFI Puppet::Util::Windows::Process module
Title: Message Title Rob Reynolds commented on an issue Re: FFI Puppet::Util::Windows::Process module And waiting for the win32_bool update to roll in to make some more changes. Add Comment Puppet / PUP-838 FFI Puppet::Util::Windows::Process module This code was already FFI'ed awhile ago, but there are refactors remaining, such as relying on common DWORD definitions, and function declarations, e.g. CloseHandle. 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-1295) Yum provider purge target runs irrespective of package installation status
Title: Message Title
Hunter Haugen commented on an issue
Re: Yum provider purge target runs irrespective of package installation status
Still seeing this issue, Puppet 3.6.1, CentOS 6.5, ruby 1.8.7p352
Add Comment
Puppet / PUP-1295
Yum provider purge target runs irrespective of package installation status
It seems the yum provider will try to purge an absent package: pre [root@test ~]# cat test.pp package { logwatch: ensure = purged; } [root@test ~]# /bin/rpm -q logwatch --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}' package logwatch is not installed [root@test ~]# puppet -d -v test.pp debug: 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-2287) Lambda with default valued parameter cannot be overridden
Title: Message Title
Kurt Wall commented on an issue
Re: Lambda with default valued parameter cannot be overridden
Verified in master at commit da289b1:
$ be puppet apply --parser future -e '{a=1, b = nil}.each |$k, $v=bad| { notice $k, $v }'
Notice: a, 1
Notice: b, nil
Notice: Compiled catalog for dopio.puppetlabs.com in environment production in 0.31 seconds
Notice: Finished catalog run in 0.02 seconds
Add Comment
Puppet / PUP-2287
Lambda with default valued parameter cannot be overridden
If a default value is given for a lambdas parameter it will not be overridden by a given value. The logic in evaluator_impl L 209-217 {code} given_argument = m[1] argument_name = m[0].name default_expression = m[0].value value = if default_expression evaluate(default_expression, scope) else given_argument ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the
Jira (PUP-1597) contain cannot contain a fully qualified class
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1597 contain cannot contain a fully qualified class Change By: Kurt Wall Assignee: KurtWall 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 (FACT-483) Explore extracting FACT-185 fix for use in 1.7.x
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-483 Explore extracting FACT-185 fix for use in 1.7.x Change By: Kylo Ginsberg Assignee: AdrienThebo 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 (FACT-483) Explore extracting FACT-185 fix for use in 1.7.x
Title: Message Title Kylo Ginsberg commented on an issue Re: Explore extracting FACT-185 fix for use in 1.7.x Didn't follow the state changes there, but I think Adrien's working on this so I assigned back to him. If not, unassign. Add Comment Facter / FACT-483 Explore extracting FACT-185 fix for use in 1.7.x There have been a number of customer requests for the EC2 VPC fixes that are in Facter 2. Since PE will be on 1.7.x for a while longer, it'd be nice to make these changes available in a way that customers can make use of. 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 (FACT-481) Infinite loop if EC2 metadata server times out
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Facter / FACT-481 Infinite loop if EC2 metadata server times out Change By: Kylo Ginsberg Assignee: AdrienThebo 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 (FACT-481) Infinite loop if EC2 metadata server times out
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-481 Infinite loop if EC2 metadata server times out Change By: Kylo Ginsberg Sprint: Week2014-5- 28 21 to2014- 6 5 - 4 28 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 (FACT-481) Infinite loop if EC2 metadata server times out
Title: Message Title Kylo Ginsberg commented on an issue Re: Infinite loop if EC2 metadata server times out Okay I'm starting on the revert entertainment. Add Comment Facter / FACT-481 Infinite loop if EC2 metadata server times out On a Rackspace VM, Facter gets into an infinite loop when trying to contact the EC2 metadata server. The retry loop in lib/facter/ec2/rest.rb doesn't increment the counter on each iteration. This causes the Puppet agent to permanently hang. To reproduce on a non-Rackspace system, just run: FACTER_virtual=xen bin/facter (Assuming there's no metada... 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 (HI-254) Docs pushed
Title: Message Title Henrik Lindberg commented on an issue Re: Docs pushed is there anything left to do on this? Please mark as resolved if not. Add Comment Hiera / HI-254 Docs pushed Push the documentation updates to docs.puppetlabs.com. Dependencies: * Go / No Go meeting (Status - Ship it!) 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 (FACT-481) Infinite loop if EC2 metadata server times out
Title: Message Title Kylo Ginsberg commented on an issue Re: Infinite loop if EC2 metadata server times out Okay reverted facter/stable. Then merged stable to facter-2 and reverted that (so no net change to facter-2 branch). I'll keep an eye on it through CI. Add Comment Facter / FACT-481 Infinite loop if EC2 metadata server times out On a Rackspace VM, Facter gets into an infinite loop when trying to contact the EC2 metadata server. The retry loop in lib/facter/ec2/rest.rb doesn't increment the counter on each iteration. This causes the Puppet agent to permanently hang. To reproduce on a non-Rackspace system, just run: FACTER_virtual=xen bin/facter (Assuming there's no metada... 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 (FACT-481) Infinite loop if EC2 metadata server times out
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-481 Infinite loop if EC2 metadata server times out Change By: Kylo Ginsberg Affects Version/s: 2.0.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-514) Add optional type to parameters
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Add optional type to parameters
Sorry fat-fingered a move. I restored this to Ready for Merge.
Add Comment
Puppet / PUP-514
Add optional type to parameters
It is of great value to be able to optionally type the parameters of defines and classes (as well as types). This is quite easy to implement as there now is a type system. The default type is Optional[Variant[Object,Type]] i.e. anything To optionally type a parameter simply enter the type before the parameter: {code} define foo(String $x, Integ...
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-121) Remove relative namespacing
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-121 Remove relative namespacing Change By: Joshua Partlow Sprint: Week2014-5- 28 21 to2014- 6 5 - 4 28 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 (FACT-481) Infinite loop if EC2 metadata server times out
Title: Message Title Kylo Ginsberg commented on an issue Re: Infinite loop if EC2 metadata server times out New pull against facter-2 merged. Add Comment Facter / FACT-481 Infinite loop if EC2 metadata server times out On a Rackspace VM, Facter gets into an infinite loop when trying to contact the EC2 metadata server. The retry loop in lib/facter/ec2/rest.rb doesn't increment the counter on each iteration. This causes the Puppet agent to permanently hang. To reproduce on a non-Rackspace system, just run: FACTER_virtual=xen bin/facter (Assuming there's no metada... 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-2314) assert_type function should handle lambda
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2314 assert_type function should handle lambda Change By: Joshua Partlow Sprint: Week2014-5- 28 21 to2014- 6 5 - 4 28 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 (FACT-449) Facter is very slow in presence of large number of network interfaces
Title: Message Title Zachary Stern updated an issue Facter / FACT-449 Facter is very slow in presence of large number of network interfaces Change By: Zachary Stern Labels: customersupport 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-2314) assert_type function should handle lambda
Title: Message Title
Joshua Partlow commented on an issue
Re: assert_type function should handle lambda
Merged to master in e960d2d
Add Comment
Puppet / PUP-2314
assert_type function should handle lambda
The assert_type function was written before lambda support was added to the new function API. If called like this: {code} assert_type(Callable[Optional[Object]]) |$x| { } {code} It fails because it does not support an optional lambda being passed. (The error message is also hard to understand - this is a separate issue). This is easily fixed b...
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-2632) Type type is not an Object
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2632 Type type is not an Object Change By: Joshua Partlow Sprint: Week2014-5- 28 21 to2014- 6 5 - 4 28 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-2632) Type type is not an Object
Title: Message Title Joshua Partlow commented on an issue Re: Type type is not an Object Merged to master in e960d2d Add Comment Puppet / PUP-2632 Type type is not an Object It seemed to be a good idea to make the Type type not be an Object, but this creates difficulties when a type is needed for anything as it has to be written as Optional[Variant[Type, Object]], which is a horrible construct to begin with, and it will be shown in error messages for all untyped since it has to be the default for accepting anything. 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 https://groups.google.com/d/optout.
Jira (PUP-867) Deprecate Dynamically Scope Resource Defaults
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-867 Deprecate Dynamically Scope Resource Defaults Change By: Henrik Lindberg Sprint: Week2014-5- 28 21 to2014- 6 5 - 4 28 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-867) Deprecate Dynamically Scope Resource Defaults
Title: Message Title
Joshua Partlow commented on an issue
Re: Deprecate Dynamically Scope Resource Defaults
merged to master in 140105
Add Comment
Puppet / PUP-867
Deprecate Dynamically Scope Resource Defaults
Currently the manifest {code} class a { Notify { message = defaulted } include b notify { bye: } } class b { notify { hi: } } include a {code} results in {code} Notice: Compiled catalog for aparker.delivery.puppetlabs.net in environment production in 0.02 seconds Notice: defaulted Notice: /Stage[main]/B/Notify[h...
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-745) Windows does not support :links :follow on symlinks
Title: Message Title Rob Reynolds commented on an issue Re: Windows does not support :links :follow on symlinks Ethan Brown Andy Parker can we close this one as a duplicate? Add Comment Puppet / PUP-745 Windows does not support :links :follow on symlinks With the addition of Windows symlink support, interesting behavior was discovered with respect to setting `:link` to `:follow` instead of the default `:manage` behavior. There is one test that verifies the existing behavior that was last active in 2010, and was re-enabled during the work on symlinks. However, this test has been set to pending as Windo... 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 (FACT-483) Explore extracting FACT-185 fix for use in 1.7.x
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-483 Explore extracting FACT-185 fix for use in 1.7.x Change By: Kylo Ginsberg Assignee: AdrienThebo EricSorenson 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-745) Windows does not support :links :follow on symlinks
Title: Message Title Ethan Brown commented on an issue Re: Windows does not support :links :follow on symlinks FWIR, not a dupe. This test is still marked as pending https://github.com/puppetlabs/puppet/blob/master/spec/unit/type/file_spec.rb#L1382 Add Comment Puppet / PUP-745 Windows does not support :links :follow on symlinks With the addition of Windows symlink support, interesting behavior was discovered with respect to setting `:link` to `:follow` instead of the default `:manage` behavior. There is one test that verifies the existing behavior that was last active in 2010, and was re-enabled during the work on symlinks. However, this test has been set to pending as Windo... 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-840) FFI Puppet::Util::Colors module
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Puppet / PUP-840 FFI Puppet::Util::Colors module Change By: Joshua Cooper Assignee: JoshuaCooper 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-840) FFI Puppet::Util::Colors module
Title: Message Title
Joshua Cooper commented on an issue
Re: FFI Puppet::Util::Colors module
Merged into master in 3cafcd4d6 to be released in 3.7.0
Add Comment
Puppet / PUP-840
FFI Puppet::Util::Colors module
In order to maintain compatibility with ruby 1.9.x, this ticket is about FFI'ing the {{Puppet::Util::Colors}} module, so use FFI instead of: {code} WriteConsole = Win32API.new( kernel32, WriteConsoleW, ['l', 'p', 'l', 'p', 'p'], 'l' ) {code} We should always prefer wide character APIs, and not make assumptions about pointer lengths: {code} ...
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-838) FFI Puppet::Util::Windows::Process module
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-838 FFI Puppet::Util::Windows::Process module Change By: Joshua Cooper Assignee: JoshuaCooper 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-838) FFI Puppet::Util::Windows::Process module
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Puppet / PUP-838 FFI Puppet::Util::Windows::Process module Change By: Joshua Cooper Assignee: JoshuaCooper 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-838) FFI Puppet::Util::Windows::Process module
Title: Message Title Ethan Brown commented on an issue Re: FFI Puppet::Util::Windows::Process module Merged to master in https://github.com/puppetlabs/puppet/commit/8cc786b44cded621903592cdea692a67c9510a9e Added a couple of additional commits / tests Add Comment Puppet / PUP-838 FFI Puppet::Util::Windows::Process module This code was already FFI'ed awhile ago, but there are refactors remaining, such as relying on common DWORD definitions, and function declarations, e.g. CloseHandle. 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-2656) FFI Puppet::Util::Windows::Registry
Title: Message Title Ethan Brown created an issue Puppet / PUP-2656 FFI Puppet::Util::Windows::Registry Issue Type: Task Assignee: Unassigned Created: 23/May/14 5:56 PM Priority: Normal Reporter: Ethan Brown Need to FFI require 'windows/national' Windows::National::GetACP.call Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2656) FFI Puppet::Util::Windows::Registry
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2656 FFI Puppet::Util::Windows::Registry Change By: Ethan Brown Sprint: Week2014-5-28to2014-6-4 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-2657) FFI Puppet::Util::Windows::Error
Title: Message Title Ethan Brown created an issue Puppet / PUP-2657 FFI Puppet::Util::Windows::Error Issue Type: Task Assignee: Unassigned Created: 23/May/14 5:58 PM Fix Versions: 3.7.0 Priority: Normal Reporter: Ethan Brown Need to FFI def initialize(message, code = GetLastError.call, original = nil) Add Comment
Jira (PUP-2656) FFI Puppet::Util::Windows::Registry
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2656 FFI Puppet::Util::Windows::Registry Change By: Ethan Brown Fix Version/s: 3.7.0 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-2657) FFI Puppet::Util::Windows::Error
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2657 FFI Puppet::Util::Windows::Error Change By: Ethan Brown Sprint: Week2014-5-28to2014-6-4 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-2657) FFI Puppet::Util::Windows::Error
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2657 FFI Puppet::Util::Windows::Error Change By: Ethan Brown Sprint: Week2014-5- 28 21 to2014- 6 5 - 4 28 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-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title mike jeski commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log same issue here with 3.6.1 on Ubuntu 12.04.4 and Debian Squeeze Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log 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-2382) Standardize existing FFI code and refactor where necessary
Title: Message Title Rob Reynolds commented on an issue Re: Standardize existing FFI code and refactor where necessary Merged into master at 130985e to be released in 3.7.0. Add Comment Puppet / PUP-2382 Standardize existing FFI code and refactor where necessary We need to standardize on how windows types, e.g. DWORD, HANDLE, etc are represented in FFI, and refactor places where duplicate methods are defined, e.g. CloseHandle, etc. 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-745) Windows does not support :links :follow on symlinks
Title: Message Title Rob Reynolds commented on an issue Re: Windows does not support :links :follow on symlinks Ah that's what you meant in chat. So not a dupe, but PUP-1192 didn't bring in follow either then eh? Add Comment Puppet / PUP-745 Windows does not support :links :follow on symlinks With the addition of Windows symlink support, interesting behavior was discovered with respect to setting `:link` to `:follow` instead of the default `:manage` behavior. There is one test that verifies the existing behavior that was last active in 2010, and was re-enabled during the work on symlinks. However, this test has been set to pending as Windo... 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
