Jira (PUP-3186) Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory
Title: Message Title Yann HAMON created an issue Puppet / PUP-3186 Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory Issue Type: Bug Affects Versions: 3.7.0 Assignee: Andy Parker Components: Server Created: 05/Sep/14 4:49 AM Priority: Normal Reporter: Yann HAMON We use puppet environments, and symlink the puppet folder of one of our git repos to /etc/puppet/environment. This is how it looks like: #:/etc/puppet/environments$ ls -l total 4 lrwxrwxrwx 1 root root 47 Jul 4 10:05 user1 - /var/lib/ops-automation.user1/puppet lrwxrwxrwx 1 root root 49 Jul 4 10:05 user2 - /var/lib/ops-automation.user2/puppet lrwxrwxrwx 1 root root 49 Jul 4 10:05 production - /var/lib/ops-automation.production/puppet After we upgraded to puppet 3.7.0 this morning, Puppet would remove the symlink /etc/puppet/environment/production and replace it with an empty folder. Reverting to 3.6.2 fixed the issue for us. I suspect it might be linked to this patch: https://github.com/puppetlabs/puppet/pull/2646/files#diff-13 It seems to ensure the environment folder is a directory and manage it if this, among other things, is true: Puppet::FileSystem.exist?(envdir) Though in our case, the file exists but isn't a directory. If I'm right with
Jira (PUP-3187) Puppet file parameter selinux_ignore_defaults doesn't work as expected
Title: Message Title Filip Pytloun created an issue Puppet / PUP-3187 Puppet file parameter selinux_ignore_defaults doesn't work as expected Issue Type: Bug Affects Versions: 3.7.0, 3.4.3 Assignee: Unassigned Created: 05/Sep/14 7:00 AM Priority: Normal Reporter: Filip Pytloun Purpose https://docs.puppetlabs.com/references/latest/type.html#file-attribute-selinux_ignore_defaults selinux_ignore_defaults If this is set then Puppet will not ask SELinux (via matchpathcon) to supply defaults for the SELinux attributes (seluser, selrole, seltype, and selrange). In general, you should leave this set at its default and only set it to true when you need Puppet to not try to fix SELinux labels automatically. Valid values are true, false. If this parameter is true, selinux label should not be changed when file is updated by Puppet. However behavior is the same as it's false but without output about changed label. Our problem is following: Puppet run is executed (our SELinux policies are not installed yet) Puppet loads currently present policies at the begining
Jira (PDB-862) PR (137): Fix some Puppet Lint errors - baurmatt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-862 PR (137): Fix some Puppet Lint errors - baurmatt Issue Type: Task Assignee: Unassigned Created: 05/Sep/14 9:56 AM Labels: github module Priority: Normal Reporter: gepetto-bot Fix some Puppet Lint errors Author: Matthias Baur Company: dmc digital media center GmbH Github ID: baurmatt Pull Request 137 Discussion Pull Request 137 File Diff Pull Request Description As mention in the subject, i've fixed some Puppet lint errors. Regards, Matthias (webhooks-id: 5c9c549d2a708ce054e917c87233d9cc)
Jira (PUP-900) noop = true is ignored when resource is triggered by other resource
Title: Message Title
Adrien Thebo commented on an issue
Re: noop = true is ignored when resource is triggered by other resource
Jason Antman this has actually been on my hit list for a while; I did the preliminary work to figure out what's going on in https://github.com/puppetlabs/puppet/commit/230667aed533186504cb916e06bae1d6011a4bf6 so this wasn't as hardcore as it may seem. I'm glad we could get this solved for you!
Add Comment
Puppet / PUP-900
noop = true is ignored when resource is triggered by other resource
when running : {code} file {'/tmp/asd': content = generate('/bin/date'), notify = Exec['ttt'], }exec { 'ttt': command ='/bin/date', logoutput = true, noop = true, } {code} exec is still ran even tho it's set to noop, any notify to resource makes it ignore noop parameter: {cod...
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
Jira (PUP-3189) Support https, http, other URI schemes in file resource source parameter
Title: Message Title Reid Vandewiele updated an issue Puppet / PUP-3189 Support https, http, other URI schemes in file resource source parameter Change By: Reid Vandewiele Labels: tse 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-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Change By: Joshua Partlow Assignee: JoshuaPartlow 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-3177) Resource titles ending with square brackets fail
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3177 Resource titles ending with square brackets fail Change By: Joshua Partlow Assignee: JoshuaPartlow 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-3177) Resource titles ending with square brackets fail
Title: Message Title Joshua Partlow assigned an issue to Unassigned Puppet / PUP-3177 Resource titles ending with square brackets fail Change By: Joshua Partlow Assignee: JoshuaPartlow 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-862) PR (137): Fix some Puppet Lint errors - baurmatt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-862 PR (137): Fix some Puppet Lint errors - baurmatt Change By: Kenneth Barber Story Points: 0 Fix Version/s: module-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 (PDB-862) PR (137): Fix some Puppet Lint errors - baurmatt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-862 PR (137): Fix some Puppet Lint errors - baurmatt Change By: Kenneth Barber Sprint: 20140827to20140910 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-2411) Remove 1.8.7 multibyte string support in Lexer2
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2411 Remove 1.8.7 multibyte string support in Lexer2 Change By: Joshua Partlow Assignee: JoshuaPartlow 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-851) PR (136): OpenBSD support - buzzdeee
Title: Message Title gepetto-bot commented on an issue Re: PR (136): OpenBSD support - buzzdeee Pull request OpenBSD support has been closed. Add Comment PuppetDB / PDB-851 PR (136): OpenBSD support - buzzdeee h2. OpenBSD support * Author: Sebastian Reitenbach sebas...@l00-bugdead-prods.de * Company: * Github ID: [buzzdeee|https://github.com/buzzdeee] * [Pull Request 136 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/136] * [Pull Request 136 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/136/files] h2. Pull Request... 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-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3162 Block $environment in directory based environment configuration settings Change By: Joshua Partlow Assignee: JoshuaPartlow 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-863) Fix JMX MQ endpoints to use new puppetlabs.puppetdb namespace
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-863 Fix JMX MQ endpoints to use new puppetlabs.puppetdb namespace Issue Type: Task Assignee: Unassigned Created: 05/Sep/14 11:34 AM Fix Versions: 3.0.0 Priority: Normal Reporter: Kenneth Barber PDB-843 introduces the change to our namespace, but we had to keep pinning the JMX and MQ names to the old namespace for backwards compatibility purposes. This ticket should be about changing these endpoints to the new values. Add Comment
Jira (PUP-2745) Puppet 3.6.1 issue with Forge API v3
Title: Message Title garrett honeycutt commented on an issue Re: Puppet 3.6.1 issue with Forge API v3 (master) bam:pkg$ puppet module install ghoneycutt-puppet --version 2.11.2 -i foo/ Notice: Preparing to install into /Users/gh/git/puppet-module-puppet/pkg/foo ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Error: bad URI(is not URI?): /v3/releases?module=ghoneycutt-generic= 1.0.0 Error: Try 'puppet help module install' for usage (master) bam:pkg$ puppet -V 3.6.1 Add Comment Puppet / PUP-2745 Puppet 3.6.1 issue with Forge API v3 Getting this error on RHEL5 and RHEL6 when trying to install ghoneycutt/puppet. Broken on 3.6.0 and 3.6.1 but downgrading to 3.5.1 fixed the issue. [root@sbox09 ~]# puppet module install ghoneycutt/puppet --verbose --debug Notice: Preparing to install into /etc/puppet/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Debug: HT... 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
Jira (PUP-2907) Regression when pluginsyncing external facts on Windows
Title: Message Title Zachary Stern updated an issue Puppet / PUP-2907 Regression when pluginsyncing external facts on Windows 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-2745) Puppet 3.6.1 issue with Forge API v3
Title: Message Title Anderson Mills commented on an issue Re: Puppet 3.6.1 issue with Forge API v3 garrett honeycutt Are you stating that this still exists in Puppet 3.6.1? We fixed it in 3.7.0. Add Comment Puppet / PUP-2745 Puppet 3.6.1 issue with Forge API v3 Getting this error on RHEL5 and RHEL6 when trying to install ghoneycutt/puppet. Broken on 3.6.0 and 3.6.1 but downgrading to 3.5.1 fixed the issue. [root@sbox09 ~]# puppet module install ghoneycutt/puppet --verbose --debug Notice: Preparing to install into /etc/puppet/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Debug: HT... 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-2745) Puppet 3.6.1 issue with Forge API v3
Title: Message Title garrett honeycutt commented on an issue Re: Puppet 3.6.1 issue with Forge API v3 Mistake.. I just remarked this as resolved. Add Comment Puppet / PUP-2745 Puppet 3.6.1 issue with Forge API v3 Getting this error on RHEL5 and RHEL6 when trying to install ghoneycutt/puppet. Broken on 3.6.0 and 3.6.1 but downgrading to 3.5.1 fixed the issue. [root@sbox09 ~]# puppet module install ghoneycutt/puppet --verbose --debug Notice: Preparing to install into /etc/puppet/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Debug: HT... 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-3190) each no longer supported in Puppet 3.7.0
Title: Message Title Per Cederqvist created an issue Puppet / PUP-3190 each no longer supported in Puppet 3.7.0 Issue Type: Bug Affects Versions: 3.7.0 Assignee: Unassigned Created: 05/Sep/14 12:32 PM Environment: Debian 7.6 and Ubuntu 12.04. Labels: future-parser Priority: Normal Reporter: Per Cederqvist After upgrading to Puppet 3.7.0, the puppetmaster no longer recognizes the each keyword. It prints this in the log: Sep 5 19:22:56 minicfg2 puppet-master[11897]: each() is only available when parser/evaluator future is in effect on node buildhost1.lysator.liu.se The /etc/puppet/puppet.conf on the puppetmaster host looks like this: [main] logdir = /var/log/puppet vardir =
Jira (PDB-849) puppetdb install from source after rake package:boostrap RuntimeError
Title: Message Title
Niels Abspoel commented on an issue
Re: puppetdb install from source after rake package:boostrap RuntimeError
just changed the packaging_url: 'git://github.com/puppetlabs/packaging.git --branch=0.3.0' in the build_defaults.yaml So I can test against package repo version 0.3.0 and I don't see this problem, could be something related to running execution.rb in
ruby 2.1.2p95
rake 10.1.0
because branch 0.3.0 doesn't have the execution.rb
Add Comment
PuppetDB / PDB-849
puppetdb install from source after rake package:boostrap RuntimeError
I'm building an archlinux package for puppetdb, Installation commands are: 1. rake clean 2. rake package:bootstrap 3: rake install PARAMS_FILE= DESTDIR=${pkgdir} On 3 it gives me a RuntimeError: rake aborted! RuntimeError Development/packages/aur-puppetdb/src/puppetdb-2.2.0/ext/packaging/lib/packaging/util/execution.rb:27:in `ex' Development/p...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3190) each no longer supported in Puppet 3.7.0
Title: Message Title
Aron Parsons commented on an issue
Re: each no longer supported in Puppet 3.7.0
Something is definitely broken in 3.7 with the future parser. Even the example from the docs (https://docs.puppetlabs.com/puppet/latest/reference/experiments_lambdas.html#available-functions) is broken. Below is from the EL6 RPM and an unmodified puppet.conf.
rpm -V puppet
rpm -q puppet puppet-3.7.0-1.el6.noarch
puppet apply --parser future -e '$a=[1,2,3] each($a) |$value| { notice $value }
' Error: each() is only available when parser/evaluator future is in effect on node host.example.com Error: each() is only available when parser/evaluator future is in effect on node host.example.com
Add Comment
Puppet / PUP-3190
each no longer supported in Puppet 3.7.0
After upgrading to Puppet 3.7.0, the puppetmaster no longer recognizes the each keyword. It prints this in the log: {noformat} Sep 5 19:22:56 minicfg2 puppet-master[11897]: each() is only available when parser/evaluator future is in effect on node buildhost1.lysator.liu.se {noformat} The /etc/puppet/puppet.conf on the puppetmaster host looks ...
Jira (PUP-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3188 Puppet module tool no longer processes files starting with a period as erb Change By: Josh Cooper Affects Version/s: 3.7.1 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-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3188 Puppet module tool no longer processes files starting with a period as erb Change By: Josh Cooper Component/s: PMT 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-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3188 Puppet module tool no longer processes files starting with a period as erb Change By: Josh Cooper Assignee: GarethRushgrove AndersonMills 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-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3188 Puppet module tool no longer processes files starting with a period as erb Change By: Josh Cooper Labels: moduletool 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-3190) each no longer supported in Puppet 3.7.0
Title: Message Title Andy Parker updated an issue Puppet / PUP-3190 each no longer supported in Puppet 3.7.0 Change By: Andy Parker Fix Version/s: 3.7.1 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-3190) each no longer supported in Puppet 3.7.0
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3190 each no longer supported in Puppet 3.7.0 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-3190) each no longer supported in Puppet 3.7.0
Title: Message Title
Andy Parker commented on an issue
Re: each no longer supported in Puppet 3.7.0
After a little bit of searching it looks like the new loader system for functions is looking in the wrong place for system functions:
I installed 3.7.0 onto a centos6 vm and hacked up /usr/lib/ruby/site_ruby/1.8/puppet/pops/loader/module_loaders.rb to give me some info about what it is trying to load:
[root@localhost ~]# puppet apply --parser future -e '[1,2].each |$x| { notice($x) }'
indexing /usr/lib/ruby/site_ruby/1.8/puppet/pops/../../../lib/puppet/functions
found []
Error: each() is only available when parser/evaluator future is in effect on node localhost.corp.puppetlabs.net
Error: each() is only available when parser/evaluator future is in effect on node localhost.corp.puppetlabs.net
Add Comment
Puppet / PUP-3190
each no longer supported in Puppet 3.7.0
After upgrading to Puppet 3.7.0, the puppetmaster no longer recognizes the each keyword. It prints this in the log: {noformat} Sep 5 19:22:56 minicfg2 puppet-master[11897]: each() is only available when parser/evaluator future is in effect on node buildhost1.lysator.liu.se {noformat} The /etc/puppet/puppet.conf on the puppetmaster host looks ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3190) each no longer supported in Puppet 3.7.0
Title: Message Title Andy Parker updated an issue Puppet / PUP-3190 each no longer supported in Puppet 3.7.0 Change By: Andy Parker Component/s: DSL 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-3190) each no longer supported in Puppet 3.7.0
Title: Message Title Andy Parker updated an issue Puppet / PUP-3190 each no longer supported in Puppet 3.7.0 Change By: Andy Parker Priority: Normal Blocker 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-3189) Support https, http, other URI schemes in file resource source parameter
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3189 Support https, http, other URI schemes in file resource source parameter Change By: Josh Cooper Component/s: TypesandProviders Component/s: Client 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-3189) Support https, http, other URI schemes in file resource source parameter
Title: Message Title Josh Cooper commented on an issue Re: Support https, http, other URI schemes in file resource source parameter Would be good to apply the same logic to the package source parameter, e.g. for windows Add Comment Puppet / PUP-3189 Support https, http, other URI schemes in file resource source parameter Today there is a distinct gap in clean functionality in Puppet with regards to describing state such as the artifact from the build server should be deployed to a local path. The File resource does not support source parameters using standard URI schemes such as http, ftp, https, etc. We should provide a clean solution to describing this kind of state. ... 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-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title Gareth Rushgrove assigned an issue to Gareth Rushgrove Puppet / PUP-3188 Puppet module tool no longer processes files starting with a period as erb Change By: Gareth Rushgrove Assignee: AndersonMills GarethRushgrove 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-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title Anderson Mills updated an issue Puppet / PUP-3188 Puppet module tool no longer processes files starting with a period as erb Change By: Anderson Mills Fix Version/s: 3.7.1 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-3191) Symlinks to missing targets cause a File Not Found error instead of a warning
Title: Message Title Anderson Mills created an issue Puppet / PUP-3191 Symlinks to missing targets cause a File Not Found error instead of a warning Issue Type: Bug Affects Versions: 3.7.0 Assignee: Unassigned Components: PMT Created: 05/Sep/14 2:09 PM Fix Versions: 3.7.1 Priority: Minor Reporter: Anderson Mills When trying to warn about symlinks in a module that is being unpacked for any reason, we use Pathname.realpath, which gives a File Not Found error when the target of the symlink doesn't exist. Add Comment
Jira (PUP-3190) each no longer supported in Puppet 3.7.0
Title: Message Title Andy Parker updated an issue Puppet / PUP-3190 each no longer supported in Puppet 3.7.0 Change By: Andy Parker Sprint: 2014-09-17 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-3190) each no longer supported in Puppet 3.7.0
Title: Message Title Andy Parker updated an issue Puppet / PUP-3190 each no longer supported in Puppet 3.7.0 Change By: Andy Parker Story Points: 1 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-121) Add Ruby 2.0 and 2.1 to spec test matrix for puppetdb
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-121 Add Ruby 2.0 and 2.1 to spec test matrix for puppetdb Change By: Wyatt Alt Assignee: WyattAlt 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-121) Add Ruby 2.0 and 2.1 to spec test matrix for puppetdb
Title: Message Title Wyatt Alt assigned an issue to Unassigned PuppetDB / PDB-121 Add Ruby 2.0 and 2.1 to spec test matrix for puppetdb Change By: Wyatt Alt Assignee: WyattAlt 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-3174) After enabling directory environments the manifestdir setting is still required to be valid
Title: Message Title Henrik Lindberg commented on an issue Re: After enabling directory environments the manifestdir setting is still required to be valid PR added that skips manifestdir when environmentpath is set. Add Comment Puppet / PUP-3174 After enabling directory environments the manifestdir setting is still required to be valid PE gives a stack trace if the manifestdir does not exist. When setting up directory environments we recommend moving the $confdir/manifest folder into your environment which is guaranteed to break your install. https://docs.puppetlabs.com/puppet/latest/reference/environments.html Steps to reproduce: 1. Install PE3.3 on your platform of choice ... 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-179) Puppet needs to delegate all fact loading to Facter
Title: Message Title Kylo Ginsberg commented on an issue Re: Puppet needs to delegate all fact loading to Facter Peter Huene did this get done as part of adding `--cfacter` support in PUP-2104 ? Add Comment Puppet / PUP-179 Puppet needs to delegate all fact loading to Facter 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-3177) Resource titles ending with square brackets fail
Title: Message Title
Henrik Lindberg commented on an issue
Re: Resource titles ending with square brackets fail
Retargeted to 3.7.1 - new PR when paint has dried on local test run.
Add Comment
Puppet / PUP-3177
Resource titles ending with square brackets fail
Hi, We're trying to install a package but the title has got square brackets which seems to make Puppet blow up, for example: package { Windows Server AppFabric v1.1 CU4 [KB 2800726]: ensure = installed, source = $fullInstallerPath, install_options = $install_options, } Trying to run this results in err...
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-3177) Resource titles ending with square brackets fail
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3177 Resource titles ending with square brackets fail Change By: Henrik Lindberg Fix Version/s: 3.7.1 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-179) Puppet needs to delegate all fact loading to Facter
Title: Message Title Peter Huene commented on an issue Re: Puppet needs to delegate all fact loading to Facter Yep, this was fixed in PUP-2104 . The facter terminus now delegates all fact loading to the Facter implementation. Add Comment Puppet / PUP-179 Puppet needs to delegate all fact loading to Facter 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-2855) Puppet agent segfault on OSX Mavericks when puppet master is running under passenger
Title: Message Title Rudy McComb commented on an issue Re: Puppet agent segfault on OSX Mavericks when puppet master is running under passenger worked on this issue with Josh Cooper and it appears to be an issue with openssl and ruby. Yosemite ships with ruby 2.0.0p481 and Mavericks with Ruby 2.0.0p451, this issues doesn't appear to be existent in Yosemite. Here is a link to ruby bugs with the same issue https://bugs.ruby-lang.org/issues/9774 Add Comment Puppet / PUP-2855 Puppet agent segfault on OSX Mavericks when puppet master is running under passenger When running under the default WEBrick server puppet master and agents function as expected. When running under passenger agents on OSX Mavericks segfault (sorry, I don't have access to other versions of OSX currently). Agents running under CentOS 6.5 continue to function normally under passenger. Dump file attached. Here is the output: bash-3.2#... 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 (PDB-864) PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-864 PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes Issue Type: Task Assignee: Unassigned Created: 05/Sep/14 4:24 PM Labels: github module Priority: Normal Reporter: gepetto-bot Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini Author: Robin Bowes robin.bo...@yo61.com Company: YO61 Ltd Github ID: robinbowes Pull Request 138 Discussion Pull Request 138 File Diff Pull Request Description I needed to have a repeatable build for a puppetdb server, ie using the same SSL certs. This change adds the capability to deploy pre-generated keys.
Jira (PUP-179) Puppet needs to delegate all fact loading to Facter
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-179 Puppet needs to delegate all fact loading to Facter Change By: Kylo Ginsberg Fix Version/s: 4.0.0 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-2855) Puppet agent segfault on OSX Mavericks when puppet master is running under passenger
Title: Message Title
Josh Cooper commented on an issue
Re: Puppet agent segfault on OSX Mavericks when puppet master is running under passenger
We were able to reproduce the segfault crash using a simple ruby http client. I don't believe this is a puppet bug, but is an ruby/openssl compatibility issue:
require 'net/http'
require 'openssl'
server = fqdn of your puppetmaster
http = Net::HTTP.new(server, 8140)
http.use_ssl = true
http.verify_mode = OpenSSL::SSL::VERIFY_NONE
http.set_debug_output($stderr)
headers = {
Accept-Encoding = gzip;q=1.0,deflate;q=0.6,identity;q=0.3,
Accept = s
}
request = Net::HTTP::Get.new(/production/certificate/ca, headers)
puts http.request(request)
Add Comment
Puppet / PUP-2855
Puppet agent segfault on OSX Mavericks when puppet master is running under passenger
When running under the default WEBrick server puppet master and agents function as expected. When running under passenger agents on OSX Mavericks segfault (sorry, I don't have access to other versions of OSX currently). Agents running under CentOS 6.5 continue to function normally under passenger. Dump file attached. Here is the output: bash-3.2#...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
