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
Thanks for testing Doug - totally missed your followup last night
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 options, visit https://groups.google.com/d/optout.
Jira (PUP-2695) defining a class twice merges their behaviors
Title: Message Title
Daniele Sluijters commented on an issue
Re: defining a class twice merges their behaviors
I'd like to vote for changing it. I've never seen a module in the wild rely on this behaviour and if you do you sort-of deserve to rewrite it. I don't even think most people have tried this or realised that this is the case.
I'm betting that if someone stumbled upon this by accident they shrugged, renamed the class and went on their merry way. Most people consider classes to have the same requirement as types, you can't have two of the same.
It should be 'easy' enough to gauge if changing this will cause trouble. Take the top 50, 100 and 500 modules from the Forge, if no one uses this pattern you're good to kill this (I'm pretty positive not a single module on the Forge does this).
Add Comment
Puppet / PUP-2695
defining a class twice merges their behaviors
A new hire ([~erin]) is working through exercises and inadvertently defined a class twice in a file with surprising results. {code} class test { notice('testing') notify { 'first': } } class test { notice('again') notify { 'surprise!': } } include test {code} {code} [root@student ~]# puppet apply test.pp Notice: Scope(Class[T...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2687) File Names with ? cause failures with recursive copies
Title: Message Title Rmi commented on an issue Re: File Names with ? cause failures with recursive copies Hello, Yes PUP-2700 seems to be the same bug... In fact, several characters seem problematic : If I've got a file TEST#TEST in my directory : Error: /Stage[main]/Mcollective::Plugin/File[/usr/share/mcollective/plugins/mcollective/agent/TEST#TEST]/ensure: change from absent to file failed: Could not set 'file' on ensure: Error 404 on SERVER: Not Found: Could not find file_content modules/mcollective/agent/TEST%23TEST With a file TEST?TEST : Error: /Stage[main]/Mcollective::Plugin/File[/usr/share/mcollective/plugins/mcollective/agent/TEST?TEST]/ensure: change from absent to file failed: Could not set 'file' on ensure: Error 404 on SERVER: Not Found: Could not find file_content modules/mcollective/agent/TEST With a space TEST TEST : Error: /Stage[main]/Mcollective::Plugin/File[/usr/share/mcollective/plugins/mcollective/agent/TEST TEST]/ensure: change from absent to file failed: Could not set 'file' on ensure: Error 404 on SERVER: Not Found: Could not find file_content modules/mcollective/agent/TEST%20TEST No problems with all these characters with my client in 3.5.1. Thanks for your help Add Comment Puppet / PUP-2687 File Names with ? cause failures with recursive copies
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Brian Wilkins commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] puppet 3.6.0 Red Hat Enterprise Linux Server release 6.5 (Santiago) filesystems: /dev/mapper/obvg-rootvol on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda1 on /boot type ext4 (rw) /dev/mapper/obvg-homevol on /home type ext4 (rw) /dev/mapper/obvg-tmpvol on /tmp type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) Installed puppet via puppetlabs-repo (RPM) Issue showed up randomly one day, puppet had been running for a few days on VM 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 (FACT-546) facter fails when on non standard nic
Title: Message Title redmine.exporter created an issue Facter / FACT-546 facter fails when on non standard nic Issue Type: Bug Assignee: Eric Sorenson Created: 30/May/14 5:33 AM Labels: redmine customer Priority: Normal Reporter: redmine.exporter I have a nic with a ; - ;vdsmdummy; when running facter multiple errors appear sh: -c: line 0: `/sbin/arp -en -i ;vdsmdummy; | sed -e 1d' when facter generates this arp command if there's ; in the nic name it should be escaped \;vdsmdummy\; thanks Add Comment This message
Jira (FACT-546) facter fails when on non standard nic
Title: Message Title Lukas Grimm commented on an issue Re: facter fails when on non standard nic I have a similar problems on RHEV/oVirt Hypervisors. 7: ;vdsmdummy;: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff with every Puppet run I get: Info: Loading facts in /var/lib/puppet/lib/facter/acpi_available.rb sh: vdsmdummy: command not found sh: vdsmdummy: command not found sh: vdsmdummy: command not found sh: vdsmdummy: command not found sh: vdsmdummy: command not found sh: vdsmdummy: command not found sh: vdsmdummy: command not found sh: vdsmdummy: command not found sh: vdsmdummy: command not found sh: vdsmdummy: command not found sh: vdsmdummy: command not found sh: vdsmdummy: command not found sh: vdsmdummy: command not found sh: vdsmdummy: command not found Facter Version 2.0.1 Add Comment Facter / FACT-546 facter fails when on non standard nic I have a nic with a ; - ;vdsmdummy; when running facter multiple errors appear sh: -c: line 0: `/sbin/arp -en -i ;vdsmdummy; | sed -e 1d' when facter generates this arp command if there's ; in the nic name it should be escaped \;vdsmdummy\; thanks This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt updated an issue Puppet / PUP-2692 Puppet master passenger processes keep growing graph showing the transition to environment_timeout = 180 Change By: Joshua Hoblitt Attachment: graph.php.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 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-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt commented on an issue Re: Puppet master passenger processes keep growing Setting environment_timeout = 180 appears to have a similar affect on memory growth as leaving it at the default value of 5s. The graph looks a bit different in that an addition 2GB of memory was added to the VM and all processes belonging to the puppet user were put into a new cgroup with a memory limit of 8GB. The sharp peaks in the graph is the result of the OOM activating in the cgroup. Eg. Memory cgroup out of memory: Kill process 13301 (ruby) score 172 or sacrifice child Killed process 13301, UID 52, (ruby) total-vm:1569376kB, anon-rss:1441948kB, file-rss:3932kB Add Comment Puppet / PUP-2692 Puppet master passenger processes keep growing [~jhoblitt] reported on IRC in #puppet-dev that after upgrading from 3.6.0 to 3.6.1 his master processes started growing to 1.5GB. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2103) Puppet client does not update and does consult the crl during authentication
Title: Message Title Brice Figureau commented on an issue Re: Puppet client does not update and does consult the crl during authentication Erik Daln do you mean something like this: https://github.com/puppetlabs/puppet/pull/510 It might be possible to revive this feature. It just needs a couple of fixes, tests and support from Puppetlabs Add Comment Puppet / PUP-2103 Puppet client does not update and does consult the crl during authentication In my tests puppet client never updates it’s /var/lib/puppet/ssl/crl.pem from the master when it changes. Though the CRL is initially downloaded from a CA and ‘cached’ that cache is never cleared causing multi-master setups to run with an increasingly outdated CRL. I think this bug is dangerous especially because the separate CA thing is new and peo... 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-2103) Puppet client does not update and does consult the crl during authentication
Title: Message Title Erik Daln commented on an issue Re: Puppet client does not update and does consult the crl during authentication Brice Figureau yes, something like that That is only a OCSP client, right? Not a OCSP responder? Haven't read all the code yet Add Comment Puppet / PUP-2103 Puppet client does not update and does consult the crl during authentication In my tests puppet client never updates it’s /var/lib/puppet/ssl/crl.pem from the master when it changes. Though the CRL is initially downloaded from a CA and ‘cached’ that cache is never cleared causing multi-master setups to run with an increasingly outdated CRL. I think this bug is dangerous especially because the separate CA thing is new and peo... 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-2103) Puppet client does not update and does consult the crl during authentication
Title: Message Title Brice Figureau commented on an issue Re: Puppet client does not update and does consult the crl during authentication It actually does both The master respond to OCSP requests from the agents by looking at the CA CRL. And if I remind correctly the master can also check the client certificates through OCSP in the case of a remote CA. The only downside is that the protocol is not standard as it uses the Puppet REST stack whereas OCSP returns binary responses on top of HTTP. See this commit (https://github.com/masterzen/puppet/commit/eb1260e97bd4cc2fd9967b0fd1445b65312bb36a) for some explanation of the incompatibilities. It might be possible to return binary content though nowadays. Add Comment Puppet / PUP-2103 Puppet client does not update and does consult the crl during authentication In my tests puppet client never updates it’s /var/lib/puppet/ssl/crl.pem from the master when it changes. Though the CRL is initially downloaded from a CA and ‘cached’ that cache is never cleared causing multi-master setups to run with an increasingly outdated CRL. I think this bug is dangerous especially because the separate CA thing is new and peo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1498) scheduled_task won't update command
Title: Message Title c lang updated an issue Puppet / PUP-1498 scheduled_task won't update command Change By: c lang Affects Version/s: 3.6.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-1498) scheduled_task won't update command
Title: Message Title c lang commented on an issue Re: scheduled_task won't update command Confirmed this is still an issue in 3.6.0. Add Comment Puppet / PUP-1498 scheduled_task won't update command if you update a scheduled_task's command, Puppet does not make the change in the task scheduler. Other changes, e.g. the trigger, appear to work, but not the command. I've had to work around by deleting the old task and creating a new one with a different name. 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-1498) scheduled_task won't update command
Title: Message Title c lang assigned an issue to Joshua Cooper Puppet / PUP-1498 scheduled_task won't update command Change By: c lang Assignee: clang 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-2103) Puppet client does not update and does consult the crl during authentication
Title: Message Title Erik Daln commented on an issue Re: Puppet client does not update and does consult the crl during authentication It is possible to return other formats, including binary ones. It is what the msgpack patch does. There should be a string format which is basically just a binary dump of a string. Might need to override the mime type it sends though. Add Comment Puppet / PUP-2103 Puppet client does not update and does consult the crl during authentication In my tests puppet client never updates it’s /var/lib/puppet/ssl/crl.pem from the master when it changes. Though the CRL is initially downloaded from a CA and ‘cached’ that cache is never cleared causing multi-master setups to run with an increasingly outdated CRL. I think this bug is dangerous especially because the separate CA thing is new and peo... 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-2635) user purge_ssh_keys not purged
Title: Message Title Felix Frank assigned an issue to Felix Frank Puppet / PUP-2635 user purge_ssh_keys not purged Change By: Felix Frank Assignee: FelixFrank 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-2639) Increase environment_timeout default.
Title: Message Title Andy Parker assigned an issue to Unassigned Puppet / PUP-2639 Increase environment_timeout default. Change By: Andy Parker Assignee: 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-2639) Increase environment_timeout default.
Title: Message Title Joshua Partlow commented on an issue Re: Increase environment_timeout default. Discussed the arbitrariness of the timeout further with Andy Parker and Henrik Lindberg; the problem is that 'unlimited' is probably the correct default, but this requires a change in people's deployment strategies with directory environments, since simply doing a git checkout for an environment will not get any changes picked up; a graceful restart of the system is required. This seems like too big of a change for a .z release, so we will go with 3m for 3.6.2 to help cases where folks switch to directory environments without reading through all the docs and discovering that environment timeout needs tuning. And then add a patch to the puppet-4 branch changing this default to unlimited for Puppet 4. Add Comment Puppet / PUP-2639 Increase environment_timeout default. Current environment_timeout defaults to 5s, which is too quick for typically production catalog build. It is essential that the timeout be longer than the typical catalog build time, and we want a default that will work reasonable well for general production cases. Three minutes seems reasonable. This fix should be cherry picked (or merged down if al... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2692) Puppet master passenger processes keep growing
Title: Message Title Andy Parker updated an issue Puppet / PUP-2692 Puppet master passenger processes keep growing I've attached a patch (functions.patch) that can be applied to a puppet 3.6.1 installation and should get rid of most of the memory leak. I've applied it locally and run a puppet agent against a master repeatedly and it showed significant improvement in memory growth. The setup was: Directory environments enabled environment_timeout as the default value puppetlabs-apache installed in the base modulepath production directory environment with no environment specific modules production directory environment manifest is named site.pp and contains only include apache before the patch a webrick master grew very quickly from 190MB to 400MB in a matter of just a few agent runs. After the patch it took about 12 hours to reach the same size, which is what makes me think there is still a leak there, albeit a much slower one. Change By: Andy Parker Attachment: functions.patch Add Comment
Jira (PDB-280) Measure PuppetDB AWS costs by integrating it fully into Cloudability
Title: Message Title Joe Rodriguez updated an issue PuppetDB / PDB-280 Measure PuppetDB AWS costs by integrating it fully into Cloudability Change By: Joe Rodriguez Assignee: JoeRodriguez ZachLeslie 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-280) Measure PuppetDB AWS costs by integrating it fully into Cloudability
Title: Message Title Joe Rodriguez commented on an issue Re: Measure PuppetDB AWS costs by integrating it fully into Cloudability This has a new owner now. I think it is Brent Nikolaus, but I will let Zach Leslie confirm that. Add Comment PuppetDB / PDB-280 Measure PuppetDB AWS costs by integrating it fully into Cloudability [~alice] [~ken] and [~deepak] I made you all User accounts in Cloudability, you should have invites to your work address. It was suggested there that I assign this straight to you Alice. Adding [~jrod] and [~zach] as cloud service owners in Ops. We'd like to measure the cost of PuppetDB testing in AWS so we know whether we should bring it in house, ... 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-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt commented on an issue Re: Puppet master passenger processes keep growing I've applied the patch and commented out environment_timeout. We should have a good idea in about an hour. Add Comment Puppet / PUP-2692 Puppet master passenger processes keep growing [~jhoblitt] reported on IRC in #puppet-dev that after upgrading from 3.6.0 to 3.6.1 his master processes started growing to 1.5GB. 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-2404) Merge puppet 3.6 into pe-puppet 3.3.x
Title: Message Title Joshua Partlow commented on an issue Re: Merge puppet 3.6 into pe-puppet 3.3.x The 23 failures break down as follows: 9 nodes where a handful of tests fail with some variation of: * Restarting web server pe-httpd (98)Address already in use: make_sock: could not bind to address 0.0.0.0:8140 no listening sockets available, shutting down Unable to open logs Action 'start' failed. The Apache error log may have more information. ...fail! The commonality being an inability to rebind the puppet master sockets. I wonder if this is some race condition in Beaker or the service script, possibly being exposed by particular vms being slow? 1 node where a puppet module install failed to connect (I think to https://forgeapi.puppetlabs.com) http://jenkins-enterprise.delivery.puppetlabs.net/job/PE%20Puppet%20Acceptance%20Tests/87/label=modgud.delivery.puppetlabs.net,layout=64mcd,platform=oracle5/console 1 node where one of the dynamic_environments.rb agent runs was unable to connect while sending a report: http://jenkins-enterprise.delivery.puppetlabs.net/job/PE%20Puppet%20Acceptance%20Tests/87/label=modgud.delivery.puppetlabs.net,layout=32m-32d-32c,platform=ubuntu1004/consoleFull 6 32 bit nodes (sles11, centos5, scientific6, oracle5, redhat5) where use_environment_from_environmentpath.rb fails with: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node j6ty91u3vcb7yq0: Could not autoload puppet/indirector/node/console: cannot load such file -- /var/opt/lib/pe-puppet/lib/puppet/indirector/node/../../../puppetpe/puppetlabs/pe_console/console_http Add Comment
Jira (PUP-1793) Cleanup, reduce, and improve stdlib based on new Puppet 4 features
Title: Message Title Andy Parker commented on an issue Re: Cleanup, reduce, and improve stdlib based on new Puppet 4 features I don't think that fixing this is absolutely necessary for Puppet 4.0.0. The old stdlib will still work with the puppet 4 language, but will have some unneeded functions and a few gaps in functionality. I think the best approach here is to move this to the MODULES project in jira, make this the ticket that tracks a stdlib version 5, and then just clean up the functions so that stdlib v5 is the one that best fits the puppet 4 language. Add Comment Puppet / PUP-1793 Cleanup, reduce, and improve stdlib based on new Puppet 4 features 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-1244) Yum provider using version-release to validate installation.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1244 Yum provider using version-release to validate installation. Change By: Kylo Ginsberg 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-2639) Increase environment_timeout default.
Title: Message Title Joshua Partlow commented on an issue Re: Increase environment_timeout default. Merged to stable in 950e600 Add Comment Puppet / PUP-2639 Increase environment_timeout default. Current environment_timeout defaults to 5s, which is too quick for typically production catalog build. It is essential that the timeout be longer than the typical catalog build time, and we want a default that will work reasonable well for general production cases. Three minutes seems reasonable. This fix should be cherry picked (or merged down if 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-2702) Change environment_timeout default to unlimited
Title: Message Title Andy Parker created an issue Puppet / PUP-2702 Change environment_timeout default to unlimited Issue Type: Improvement Assignee: Unassigned Created: 30/May/14 10:58 AM Fix Versions: 4.0.0 Priority: Normal Reporter: Andy Parker After a lot of discussion (see PUP-2639) we agreed that the correct default for puppet's environment caching is unlimited. This is because it is the correct thing to do in a production system where deployments of new code should be a controlled affair. Require the master to reload itself for a code deploy also gets around any problems it might have for any loaded ruby code. Add Comment
Jira (PUP-2702) Change environment_timeout default to unlimited
Title: Message Title Andy Parker updated an issue Puppet / PUP-2702 Change environment_timeout default to unlimited Change By: Andy Parker 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-2702) Change environment_timeout default to unlimited
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2702 Change environment_timeout default to unlimited Change By: Andy Parker Assignee: 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-2702) Change environment_timeout default to unlimited
Title: Message Title
Joshua Partlow commented on an issue
Re: Change environment_timeout default to unlimited
Merged to puppet-4 branch in 1c9768
This should go out in Puppet 4.0
Add Comment
Puppet / PUP-2702
Change environment_timeout default to unlimited
After a lot of discussion (see PUP-2639) we agreed that the correct default for puppet's environment caching is {{unlimited}}. This is because it is the correct thing to do in a production system where deployments of new code should be a controlled affair. Require the master to reload itself for a code deploy also gets around any problems it might have fo...
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-2702) Change environment_timeout default to unlimited
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2702 Change environment_timeout default to unlimited Change By: Joshua Partlow Component/s: Modules Component/s: DOCS 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-2689) A node can't always collect its own exported resources
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2689 A node can't always collect its own exported resources Change By: Henrik Lindberg Fix Version/s: 3.6.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-2703) tag should be a statement function in future parser
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2703 tag should be a statement function in future parser Issue Type: Bug Assignee: Andy Parker Components: DSL Created: 30/May/14 11:21 AM Fix Versions: 3.7.0 Priority: Normal Reporter: Henrik Lindberg The tag function should (just like include, require, contain, and the logging functions), be considered a statement function by the future parser. Now, it is required to use parentheses around its arguments. Add Comment
Jira (PUP-2703) tag should be a statement function in future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2703 tag should be a statement function in future parser Change By: Henrik Lindberg Labels: future-parser 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-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt updated an issue Puppet / PUP-2692 Puppet master passenger processes keep growing graph of memory usage. The last hump is 3.6.1 + the functions.patch Change By: Joshua Hoblitt Attachment: graph.php.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 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-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt commented on an issue Re: Puppet master passenger processes keep growing functions.patch, after about 2 hours of run time, appears to have fixed the memory growth. +1!!! Add Comment Puppet / PUP-2692 Puppet master passenger processes keep growing [~jhoblitt] reported on IRC in #puppet-dev that after upgrading from 3.6.0 to 3.6.1 his master processes started growing to 1.5GB. 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-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2700 Puppet 3.6.1 File recurse improperly handles spaces in filenames Change By: Charlie Sharpsteen Assignee: KyloGinsberg 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 (PUP-2659) Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
Title: Message Title
Henrik Lindberg commented on an issue
Re: Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
merged to stable: a4e404f
Add Comment
Puppet / PUP-2659
Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
After upgrading puppet to version 3.6.1, the following error occurs: {noformat} Attempted to pop, but already at root of the context stack. {noformat} And afterwards log is flooded with following message: {noformat} no 'environments' in {:root_environment=#Puppet::Node::Environment:0x7fe1930f5a38 @manifest=/, @modulepath=[], @name=:*root*...
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-2659) Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
Title: Message Title
Henrik Lindberg commented on an issue
Re: Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
merged stable to master: d1723f8c38a4e075b2bce14556859be8dd8d8586
Add Comment
Puppet / PUP-2659
Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
After upgrading puppet to version 3.6.1, the following error occurs: {noformat} Attempted to pop, but already at root of the context stack. {noformat} And afterwards log is flooded with following message: {noformat} no 'environments' in {:root_environment=#Puppet::Node::Environment:0x7fe1930f5a38 @manifest=/, @modulepath=[], @name=:*root*...
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-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Puppet 3.6.1 File recurse improperly handles spaces in filenames
I haven't been able to reproduce this using a simple module containing files with spaces.
Tristan Helmich: Could you share a complete example of the failing resource declaration? Also, are you serving the files from a custom fileserver mount? If so, could you share an example of the fileserver.conf entry?
Add Comment
Puppet / PUP-2700
Puppet 3.6.1 File recurse improperly handles spaces in filenames
This one's new on me. We're using file{ : recurse = remote} to pull a directory structure from a remote puppet fileserver. It would appear that there's a mismatch causing it to multiply urlencode resources it's recursing over, causing it to render a space ' ' as %2520 in the file_content call. Here's a convenient, if ugly, example: In the Fileserv...
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-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Puppet 3.6.1 File recurse improperly handles spaces in filenames
Oops, that should have been Tristan Smith, not Tristan Helmich. Twitchy tab completion finger.
Add Comment
Puppet / PUP-2700
Puppet 3.6.1 File recurse improperly handles spaces in filenames
This one's new on me. We're using file{ : recurse = remote} to pull a directory structure from a remote puppet fileserver. It would appear that there's a mismatch causing it to multiply urlencode resources it's recursing over, causing it to render a space ' ' as %2520 in the file_content call. Here's a convenient, if ugly, example: In the Fileserv...
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-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2700 Puppet 3.6.1 File recurse improperly handles spaces in filenames Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen TristanSmith 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-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames
Title: Message Title
Tristan Smith commented on an issue
Re: Puppet 3.6.1 File recurse improperly handles spaces in filenames
Yeah, it's a custom mount on a separate fileserver. I'll do some isolation work and get you a simplified example.
Add Comment
Puppet / PUP-2700
Puppet 3.6.1 File recurse improperly handles spaces in filenames
This one's new on me. We're using file{ : recurse = remote} to pull a directory structure from a remote puppet fileserver. It would appear that there's a mismatch causing it to multiply urlencode resources it's recursing over, causing it to render a space ' ' as %2520 in the file_content call. Here's a convenient, if ugly, example: In the Fileserv...
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.
