Jira (PUP-2585) rsync mirror doesn't show http://yum.puppetlabs.com/el/7/
Title: Message Title Micha Krause commented on an issue Re: rsync mirror doesn't show http://yum.puppetlabs.com/el/7/ Yes it's working now. Add Comment Puppet / PUP-2585 rsync mirror doesn't show http://yum.puppetlabs.com/el/7/ http://yum.puppetlabs.com/el/7/ is not available via rsync: rsync yum.puppetlabs.com::packages/yum/el/7/ rsync: change_dir /yum/el/7 (in packages) failed: No such file or directory (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 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-1894) Cannot render EPP templates from a module
Title: Message Title
Henrik Lindberg commented on an issue
Re: Cannot render EPP templates from a module
The cause of this is due to passing a string with the environment name instead of an environment. It may have worked at one point when it was possible to magically use environment or its name.
Changing this to go into 3.6.1 since it pretty much blocks use of EPP in modules which is unfortunate.
Add Comment
Puppet / PUP-1894
Cannot render EPP templates from a module
According to the [module guide section about templates|http://docs.puppetlabs.com/puppet/latest/reference/modules_fundamentals.html#templates] a template is found in a module's template directory by joining the module name with the template name. However the {{epp}} function doesn't seem to be able to do this. It also does not find the template if the mod...
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
Jira (PUP-1894) Cannot render EPP templates from a module
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1894 Cannot render EPP templates from a module Change By: Henrik Lindberg Fix Version/s: 3.7.0 Fix Version/s: 3.6.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-1894) Cannot render EPP templates from a module
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1894 Cannot render EPP templates from a module Change By: Henrik Lindberg Sprint: Week2014-5-14to2014-5-21 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-2610) Rack masters lose track of environment loaders
Title: Message Title
Henrik Lindberg commented on an issue
Re: Rack masters lose track of environment loaders
Merged to stable: 0dc5ad3
Add Comment
Puppet / PUP-2610
Rack masters lose track of environment loaders
When a puppet master is running under rack the first few seconds of running will cause it to use the wrong modules if the {{[main]}} section has a different {{modulepath}} (or {{environmentpath}}) from the {{[master]}} section. Reproduction: Given a rack master with the following puppet.conf: {code} [main] modulepath = /tmp/main-modules [master]...
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-2610) Rack masters lose track of environment loaders
Title: Message Title
Henrik Lindberg commented on an issue
Re: Rack masters lose track of environment loaders
Merged to master: 4861826205335f50e9f169f25a89b9043f725825
There was a conflict in application.rb - I think I got it right but Joshua Partlow can you also take a look at the result after the merge.
Add Comment
Puppet / PUP-2610
Rack masters lose track of environment loaders
When a puppet master is running under rack the first few seconds of running will cause it to use the wrong modules if the {{[main]}} section has a different {{modulepath}} (or {{environmentpath}}) from the {{[master]}} section. Reproduction: Given a rack master with the following puppet.conf: {code} [main] modulepath = /tmp/main-modules [master]...
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-2584) Spurious warnings when using multiple file sources
Title: Message Title
Henrik Lindberg commented on an issue
Re: Spurious warnings when using multiple file sources
There were unit test failures on the PR (missing updates to specs...), this is no fixed and travis is green on the PR.
Add Comment
Puppet / PUP-2584
Spurious warnings when using multiple file sources
When a file resource uses multiple sources puppet issues a warning like (the example manifest and the warning are not intended to match in file names): {code} Warning: Find /production/file_metadata/modules/slurm/c12-8.ymir.cse.ucdavis.edu/slurm.sh?links=managesource_permissions=use resulted in 404 with the message: Not Found: Could not find file_metad...
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-239) Backport speed improvement to 1.3.x codebase
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Hiera / HI-239 Backport speed improvement to 1.3.x codebase Change By: Henrik Lindberg Assignee: HenrikLindberg 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-1135) Undeprecate 'puppet kick' run mode
Title: Message Title Rakesh Kathpal commented on an issue Re: Undeprecate 'puppet kick' run mode I too am of the the opinion that puppet kick should continue or there should be some other way to trigger a remote puppet run. Though installation of mcollective may be trivial but pushing plugins to client machines is again a pain. Imagine you are in a shared environment where you are managing customer setups using puppet. You already have puppet client sitting on their VMs and on top of it you install mcollective and plugins, it really becomes painful with multiple clients sittings on a customer machine for management. Either puppet kick or something within puppet framework itself should enable a remote puppet run. Add Comment Puppet / PUP-1135 Undeprecate 'puppet kick' run mode bq. Please not deprecate puppet kick. We use puppet in some our projects, and not use mcollective, also don’t plan use mcollective. Why? Mcollective is require mq (activemq/rabbitmq etc) and provides unneeded functionality. We can use one function from mcollective – puppet agent runonce, but why do we need to install extra software, and extra daemon on ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-867) Deprecate Dynamically Scope Resource Defaults
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-867 Deprecate Dynamically Scope Resource Defaults Change By: Henrik Lindberg Assignee: HenrikLindberg 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-676) PR (968): Fix comparison in dup resources acceptance test - kbarber
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-676 PR (968): Fix comparison in dup resources acceptance test - kbarber Issue Type: Task Assignee: Unassigned Created: 19/May/14 6:49 AM Labels: github Priority: Normal Reporter: gepetto-bot Fix comparison in dup resources acceptance test Author: Ken Barber k...@bob.sh Company: Puppet Labs Inc. Github ID: kbarber Pull Request 968 Discussion Pull Request 968 File Diff Pull Request Description Due to changes in Puppet 3.6.0, the comparison done in our resource duplication tests no longer matches the actual output. This patch ammends the comparison to match Puppet 3.6.0 output now. Signed-off-by: Ken Barber k...@bob.sh
Jira (PDB-676) PR (968): Fix comparison in dup resources acceptance test - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-676 PR (968): Fix comparison in dup resources acceptance test - kbarber Change By: Kenneth Barber 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-676) PR (968): Fix comparison in dup resources acceptance test - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-676 PR (968): Fix comparison in dup resources acceptance test - kbarber Change By: Kenneth Barber Affects Version/s: 1.6.3 Fix Version/s: 1.6.x Issue Type: Task Bug 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-676) PR (968): Fix comparison in dup resources acceptance test - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-676 PR (968): Fix comparison in dup resources acceptance test - kbarber Change By: Kenneth Barber Sprint: 20140507to20140521 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-1352) package ensure = purged is too noisy!
Title: Message Title Lee Lowder updated an issue Puppet / PUP-1352 package ensure = purged is too noisy! Change By: Lee Lowder Labels: redmine support 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-673) puppetdb installation ignores libexecdir on archlinux
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-673 puppetdb installation ignores libexecdir on archlinux 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-675) init.d script silently fails if PIDfile is missing
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-675 init.d script silently fails if PIDfile is missing 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-675) init.d script silently fails if PIDfile is missing
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-675 init.d script silently fails if PIDfile is missing This is totally the expected behaviour with the way we use start-stop-daemon in debian/ubuntu at least. We might be able to switch to using --process and --user perhaps as a fallback for do_stop in the init script, might be brutal but should work for most cases. I've at least tested this myself and it works, but I worry about clobbering other processes, perhaps that fear is unnecessary. Need to investigate. Also, Redhat-likes would require a completely different approach. Another approach might be to investigate the use of something else to manage the process, like tanukiwrapper. Change By: Kenneth Barber Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-673) puppetdb installation ignores libexecdir on archlinux
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-673 puppetdb installation ignores libexecdir on archlinux Change By: Kenneth Barber 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-673) puppetdb installation ignores libexecdir on archlinux
Title: Message Title
Kenneth Barber commented on an issue
Re: puppetdb installation ignores libexecdir on archlinux
Niels Abspoel this all smells like something isn't working the way we expect it to.
So far I've just been reading code not testing anything hoping the answer would be simple, I'll put this on our backlog to work on since I think you are correct about weirdness.
Add Comment
PuppetDB / PDB-673
puppetdb installation ignores libexecdir on archlinux
Building puppetdb package on archlinux with rake package:bootstrap rake install PARAMS_FILE= DESTDIR=${pkgdir} This provides /usr/bin/puppetdb which looks in libexec dir: /usr/libexec/puppetdb instead of /usr/lib/puppetdb. Archlinux doesn't have /usr/libexec. If I read correctly this should be set the the template task but it looks like this ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send
Jira (PDB-676) PR (968): Fix comparison in dup resources acceptance test - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (968): Fix comparison in dup resources acceptance test - kbarber pljenkinsro commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/434/ Add Comment PuppetDB / PDB-676 PR (968): Fix comparison in dup resources acceptance test - kbarber h2. Fix comparison in dup resources acceptance test * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 968 Discussion|https://github.com/puppetlabs/puppetdb/pull/968] * [Pull Request 968 File Diff|https://github.com/puppetlabs/puppetdb/pull/968/files] h2. Pull Request Desc... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDB-676) PR (968): Fix comparison in dup resources acceptance test - kbarber
Title: Message Title gepetto-bot commented on an issue Re: PR (968): Fix comparison in dup resources acceptance test - kbarber Pull request Fix comparison in dup resources acceptance test has been closed. Add Comment PuppetDB / PDB-676 PR (968): Fix comparison in dup resources acceptance test - kbarber h2. Fix comparison in dup resources acceptance test * Author: Ken Barber k...@bob.sh * Company: Puppet Labs Inc. * Github ID: [kbarber|https://github.com/kbarber] * [Pull Request 968 Discussion|https://github.com/puppetlabs/puppetdb/pull/968] * [Pull Request 968 File Diff|https://github.com/puppetlabs/puppetdb/pull/968/files] h2. Pull Request Desc... 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-675) init.d script silently fails if PIDfile is missing
Title: Message Title
Kenneth Barber commented on an issue
Re: init.d script silently fails if PIDfile is missing
Moses Mendoza, Matthaus Owens, Melissa Stone ... comments/ideas welcome on this one.
Add Comment
PuppetDB / PDB-675
init.d script silently fails if PIDfile is missing
Debugging log: init.d restart fails but silently exits 0. Missing pidfile but still running application -- killing application fixes issue. {code}# sh -x /etc/init.d/puppetdb stop + [ -r /etc/default/puppetdb ] + . /etc/default/ + [ -f /usr/lib/jvm/java-7-openjdk-amd64/bin/java ] + JAVA_BIN=/usr/lib/jvm/java-7-openjdk-amd64/bin/java + JAVA_ARGS=-X...
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-239) Backport speed improvement to 1.3.x codebase
Title: Message Title Kylo Ginsberg updated an issue Hiera / HI-239 Backport speed improvement to 1.3.x codebase Change By: Kylo Ginsberg Sprint: Week2014-5- 21 14 to2014-5- 28 21 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
Henrik Lindberg commented on an issue
Re: Deprecate Dynamically Scope Resource Defaults
PR adds the specified behavior.
It would be possible to issue a warning by comparing 4x and 3x result and issue a warning if they differ. (Will take a bit of performance to do so since this means resolving defaults twice - the new lookup is faster since it does not have to visit more than self, inherited, and enclosing scopes (typically 2-3 scopes) and for each do a lookup and copy name/values over to resulting hash, then a hash compare).
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
Jira (PUP-2582) Enable TLSv1.2 in apache vhost config
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2582 Enable TLSv1.2 in apache vhost config Change By: Joshua Cooper Ourapachevhostconfigurationisusedwhenbuildingpassengerpackagesondebian.Itwasaddedin[d85d73c|https://github.com/puppetlabs/puppet/commit/d85d73c570a60891607d2ce5b42dba4617f4ca6c]andhasn'tbeenupdatedsince.Thanksgoesto[~azet]forbringingthistoourattentionin #2492 PUP-2177 .However,we'verunintoaproblemcreatingasingleciphersuitestringthatworkscorrectlyinopenssl [ versions 0.9.7m , =version 1.0.0a ) , and versions= 1.0.0a andup .See discussionathttps://github.com/puppetlabs/puppet/pull/2494and http://marc.info/?l=openssl-devm=139993778731161w=2Wewouldliketomergeasubsetofthechangesproposedin #2492 PUP-2177 forimmediatereleasein3.6.1.Specifically,addingsupportforTLSv1.2,removingAECDH, andotherinsecurealgorithms,e.g DES, etc MD5 .Oncethecompatibilityissuesdescribedin #2492 PR2494 areresolved,we'llbringin the those changes describedin#2492 ,whichoptimizefor evengreatersecurity,suchas PFS. 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-2609) Change default of source_permissions to :ignore on Windows
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2609 Change default of source_permissions to :ignore on Windows Change By: Joshua Cooper 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-2607) environmentpath does not work in master section of config
Title: Message Title Joshua Partlow commented on an issue Re: environmentpath does not work in master section of config I think this is a duplicate of PUP-2610, based on the environment being Apache/Passenger. Add Comment Puppet / PUP-2607 environmentpath does not work in master section of config http://docs.puppetlabs.com/puppet/latest/reference/environments.html#enabling-directory-environments https://groups.google.com/forum/#!topic/puppet-users/llsPMQOjGR4 The environmentpath setting works in [main] only. Even though configprint shows it is still there when moved to [master] and the modulepath looks correct also, but the puppet master do... 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-2584) Spurious warnings when using multiple file sources
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2584 Spurious warnings when using multiple file sources 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-1894) Cannot render EPP templates from a module
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-1894 Cannot render EPP templates from a module Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2609) Change default of source_permissions to :ignore on Windows
Title: Message Title Rob Reynolds commented on an issue Re: Change default of source_permissions to :ignore on Windows Shouldn't this be for all platforms? Add Comment Puppet / PUP-2609 Change default of source_permissions to :ignore on Windows When we added the source_permissions attribute in Puppet 3.4, we marked the default value (:use) as deprecated on Windows, since it basically wreaks havoc at all times. The 4.0 boundary is a good time to follow through on that deprecation and flip the default to :ignore on Windows. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2609) Change default of source_permissions to :ignore on Windows
Title: Message Title Nicholas Fagerlund commented on an issue Re: Change default of source_permissions to :ignore on Windows Good question! It's not catastrophic on *nix the way it is on Windows, but it IS surprising to a user who hasn't already read up on it; principle of least surprise says flip it everywhere. Also, flipping for all platforms would be easier to explain, which is a good thing in and of itself. I'm in favor. Eric Sorenson? Add Comment Puppet / PUP-2609 Change default of source_permissions to :ignore on Windows When we added the source_permissions attribute in Puppet 3.4, we marked the default value (:use) as deprecated on Windows, since it basically wreaks havoc at all times. The 4.0 boundary is a good time to follow through on that deprecation and flip the default to :ignore on Windows. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send
Jira (PUP-2609) Change default of source_permissions to :ignore on Windows
Title: Message Title Nicholas Fagerlund commented on an issue Re: Change default of source_permissions to :ignore on Windows Also, unlike in ancient versions of puppet where files were expected to come out of a static mount point, we expect most files these days to come out of modules. Those modules probably came out of version control, and had the default permissions for the current user applied as they hit disk. Which means the intended source permissions are actually null, regardless of what the permissions on disk happen to be. Add Comment Puppet / PUP-2609 Change default of source_permissions to :ignore on Windows When we added the source_permissions attribute in Puppet 3.4, we marked the default value (:use) as deprecated on Windows, since it basically wreaks havoc at all times. The 4.0 boundary is a good time to follow through on that deprecation and flip the default to :ignore on Windows. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails
Jira (PUP-2609) Change default of source_permissions to :ignore on Windows
Title: Message Title
Joshua Cooper updated an issue
Puppet / PUP-2609
Change default of source_permissions to :ignore on Windows
Change By:
Joshua Cooper
Whenweaddedthesource_permissionsattributeinPuppet3.4,wemarkedthe defaultvalue( values{{ :use ) }}and{{:use_when_creating}} asdeprecatedonWindows,sinceitbasicallywreakshavocatalltimes.The4.0boundaryisagoodtimetofollowthroughonthatdeprecationand flipthedefault makesettingthesevalues to anythingotherthan{{ :ignore }}anerror onWindows .
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-2609) Don't allow source_permissions to be set to anything other than ignore on Windows
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2609 Don't allow source_permissions to be set to anything other than ignore on Windows Change By: Joshua Cooper Summary: Changedefaultof Don'tallow source_permissionsto : besettoanythingotherthan ignoreonWindows 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-2609) Don't allow source_permissions to be set to anything other than ignore on Windows
Title: Message Title
Joshua Cooper commented on an issue
Re: Don't allow source_permissions to be set to anything other than ignore on Windows
Nicholas FagerlundEric Sorenson I've added a link to the original puppet-users discussion around this behavior. The plan was to deprecate the old default :use behavior on all platforms, and at the next major boundary switch to :ignore on all platforms.
Secondarily, for Windows agents, we wanted to make it an error to set the value to anything other than :ignore on Windows, since that wreaks havoc at all times. There is already a deprecation warning in place covering this.
I've updated this ticket to cover the latter. I will file a new ticket against 3.7 to add a deprecation for the default :use behavior for all platforms, and a 4.0 ticket to switch the default behavior for all platforms. Make sense?
Add Comment
Puppet / PUP-2609
Don't allow source_permissions to be set to anything other than ignore on Windows
When we added the source_permissions attribute in Puppet 3.4, we marked the values {{:use}} and {{:use_when_creating}} as deprecated on Windows, since it basically wreaks havoc at all times. The 4.0 boundary is a good time to follow through on that deprecation and make setting these values to anything other than {{:ignore}} an error on Windows
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2613) Change source_permissions default to :ignore
Title: Message Title Joshua Cooper created an issue Puppet / PUP-2613 Change source_permissions default to :ignore Issue Type: Task Assignee: Unassigned Created: 19/May/14 10:41 AM Fix Versions: 4.0.0 Priority: Normal Reporter: Joshua Cooper Currently, puppet will copy the owner/group/mode from sourced files when those properties are unspecified. This leads to surprising results, e.g. PUP-1986 . We discussed changing the default behavior in https://groups.google.com/forum/#!msg/puppet-users/XNy8gI3jcf0/HufQkYQdKMAJ This ticket calls for changing the default value of :source_permissions from :use to :ignore on all platforms. If owner, group, and/or mode are unspecified, then the resulting file resource should have permissions based on the current user's umask (POSIX) or default dacl (Windows). Add Comment
Jira (PUP-2614) Deprecate default source_permissions :use on all platforms
Title: Message Title Joshua Cooper created an issue Puppet / PUP-2614 Deprecate default source_permissions :use on all platforms Issue Type: Task Assignee: Unassigned Created: 19/May/14 10:44 AM Fix Versions: 3.7.0 Priority: Normal Reporter: Joshua Cooper Currently, puppet will copy the owner/group/mode from sourced files when those properties are unspecified. This leads to surprising results, e.g. PUP-1986 . We discussed changing the default behavior in https://groups.google.com/forum/#!msg/puppet-users/XNy8gI3jcf0/HufQkYQdKMAJ This ticket is about issuing a deprecation warning when :source_permissions defaults to :use for all platforms. In 4.0, the default value will be changed to :ignore for all platforms. See PUP-2613. Add Comment
Jira (PUP-2614) Deprecate default source_permissions :use on all platforms
Title: Message Title
Joshua Cooper updated an issue
Puppet / PUP-2614
Deprecate default source_permissions :use on all platforms
Change By:
Joshua Cooper
Currently,puppetwillcopytheowner/group/modefromsourcedfileswhenthosepropertiesareunspecified.Thisleadstosurprisingresults,e.g.PUP-1986.Wediscussedchangingthedefaultbehaviorinhttps://groups.google.com/forum/#!msg/puppet-users/XNy8gI3jcf0/HufQkYQdKMAJThisticketisaboutissuingadeprecationwarningwhen{{:source_permissions}}defaultsto{{:use}}forallplatforms. Iftheuserexplicitlyspecifies:useor:use_when_creating,thenitshouldnotgenerateadeprecationwarningonPOSIXagents.ForWindowsagents,itshouldcontinuetoissueadeprecationwarningasitalreadydoes. In4.0,thedefaultvaluewillbechangedto{{:ignore}}forallplatforms.SeePUP-2613.
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-2568) Cannot use class references with upper cased strings
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2568 Cannot use class references with upper cased strings 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 (PUP-2421) stringify_facts needs to be in agent, not master conf file
Title: Message Title Justin Holguin assigned an issue to Justin Holguin Puppet / PUP-2421 stringify_facts needs to be in agent, not master conf file Change By: Justin Holguin Assignee: EricSorenson JustinHolguin 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-2609) Don't allow source_permissions to be set to anything other than ignore on Windows
Title: Message Title
Eric Sorenson commented on an issue
Re: Don't allow source_permissions to be set to anything other than ignore on Windows
sounds good to me. +1
Add Comment
Puppet / PUP-2609
Don't allow source_permissions to be set to anything other than ignore on Windows
When we added the source_permissions attribute in Puppet 3.4, we marked the values {{:use}} and {{:use_when_creating}} as deprecated on Windows, since it basically wreaks havoc at all times. The 4.0 boundary is a good time to follow through on that deprecation and make setting these values to anything other than {{:ignore}} an error on Windows
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2581) Interpolated variables with leading underscore regression
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-2581 Interpolated variables with leading underscore regression Change By: Ethan Brown Assignee: EthanBrown 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-1894) Cannot render EPP templates from a module
Title: Message Title
Joshua Partlow updated an issue
Puppet / PUP-1894
Cannot render EPP templates from a module
Change By:
Joshua Partlow
Accordingtothe[moduleguidesectionabouttemplates|http://docs.puppetlabs.com/puppet/latest/reference/modules_fundamentals.html#templates]atemplateisfoundinamodule'stemplatedirectorybyjoiningthemodulenamewiththetemplatename.Howeverthe{{epp}}functiondoesn'tseemtobeabletodothis.Italsodoesnotfindthetemplateifthemodulenameisleftoff.h2.Example{noformat}tree~/.puppet/environments/foo/modules//Users/andy/.puppet/environments/foo/modules/└──foo├──manifests│└──init.pp└──templates├──template.epp└──template.erbcat~/.puppet/environments/foo/modules/foo/templates/template.epp%=$x%cat~/.puppet/environments/foo/modules/foo/templates/template.erb%=@value%cat~/.puppet/environments/foo/modules/foo/manifests/init.ppclassfoo($value){notice(epp(foo/template.epp ) ,{x=$value}) ) notice(template(foo/template.erb))}bepuppetapply-eclass{foo:value=3}--parserfuture--environmentfooError:EvaluationError:ErrorwhileevaluatingaFunctionCall,undefinedmethod`module'forfoo:Stringat/Users/andy/.puppet/environments/foo/modules/foo/manifests/init.pp:2:10onnodeaparker.corp.puppetlabs.netError:EvaluationError:ErrorwhileevaluatingaFunctionCall,undefinedmethod`module'forfoo:Stringat/Users/andy/.puppet/environments/foo/modules/foo/manifests/init.pp:2:10onnodeaparker.corp.puppetlabs.net{noformat}Uncommentingtheepplineshowsthattheerblineworks.
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
Jira (PUP-1894) Cannot render EPP templates from a module
Title: Message Title
Joshua Partlow commented on an issue
Re: Cannot render EPP templates from a module
Merged to stable in d0e310
Add Comment
Puppet / PUP-1894
Cannot render EPP templates from a module
According to the [module guide section about templates|http://docs.puppetlabs.com/puppet/latest/reference/modules_fundamentals.html#templates] a template is found in a module's template directory by joining the module name with the template name. However the {{epp}} function doesn't seem to be able to do this. It also does not find the template if the mod...
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-1894) Cannot render EPP templates from a module
Title: Message Title
Joshua Partlow commented on an issue
Re: Cannot render EPP templates from a module
I checked that Andy's test case passed with Henrik's change. This can probably skip FR once CI passes.
Add Comment
Puppet / PUP-1894
Cannot render EPP templates from a module
According to the [module guide section about templates|http://docs.puppetlabs.com/puppet/latest/reference/modules_fundamentals.html#templates] a template is found in a module's template directory by joining the module name with the template name. However the {{epp}} function doesn't seem to be able to do this. It also does not find the template if the mod...
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-2584) Spurious warnings when using multiple file sources
Title: Message Title
Joshua Partlow commented on an issue
Re: Spurious warnings when using multiple file sources
Merged to stable in 8e473d1
Add Comment
Puppet / PUP-2584
Spurious warnings when using multiple file sources
When a file resource uses multiple sources puppet issues a warning like (the example manifest and the warning are not intended to match in file names): {code} Warning: Find /production/file_metadata/modules/slurm/c12-8.ymir.cse.ucdavis.edu/slurm.sh?links=managesource_permissions=use resulted in 404 with the message: Not Found: Could not find file_metad...
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-2581) Interpolated variables with leading underscore regression
Title: Message Title
Ethan Brown commented on an issue
Re: Interpolated variables with leading underscore regression
Verified in stable
C:\source\puppet [master +3 ~0 -0 !] git reset --hard 0d2ae9e HEAD is now at 0d2ae9e Merge branch 'pr/2656' into stable
C:\source\puppet [master +3 ~0 -0 !] cat hello.pp $_foo = 'hello world' notify { ${_foo}: }
C:\source\puppet [master +3 ~0 -0 !] bundle exec puppet apply --parser=current hello.pp Notice: Compiled catalog for vagrant-2008r2.localdomain in environment production in 0.06 seconds Notice: hello world Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world' Notice: Finished catalog run in 0.37 seconds
C:\source\puppet [master +3 ~0 -0 !] bundle exec puppet apply --parser=future hello.pp Error: Could not parse for environment production: Syntax error at '_' at C:/source/puppet/hello.pp:2:13 on node vagrant-2008r2.localdomain Error: Could not parse for environment production: Syntax error at '_' at C:/source/puppet/hello.pp:2:13 on node vagrant-2008r2.localdomain
after merged code
C:\source\puppet [master +3 ~0 -0 !] git reset --hard 75569b11d209328be9491d7ed9623ed64405e1f0 HEAD is now at 75569b1 Merge pull request #2661 from hlindberg/pup-2581_interpolating-_expression_-of-bad-name
C:\source\puppet [master +3 ~0 -0 !] bundle exec puppet apply --parser=current hello.pp Notice: Compiled catalog for vagrant-2008r2.localdomain in environment production in 0.06 seconds Notice: hello world Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world' Notice: Finished catalog run in 0.37 seconds
C:\source\puppet [master +3 ~0 -0 !] bundle exec puppet apply --parser=future hello.pp Notice: Compiled catalog for vagrant-2008r2.localdomain in environment production in 0.64 seconds Notice: hello world Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world' Notice: Finished catalog run in 0.39 seconds
Add Comment
Jira (PDB-677) Release PuppetDB 2.0.0 for Ubuntu 14.04
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-677 Release PuppetDB 2.0.0 for Ubuntu 14.04 Issue Type: Task Assignee: Unassigned Created: 19/May/14 11:43 AM Fix Versions: 2.0.0 Priority: Normal Reporter: Kenneth Barber Release PuppetDB 2.0.0 for Ubuntu 14.04. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-677) Release PuppetDB 2.0.0 for Ubuntu 14.04
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-677 Release PuppetDB 2.0.0 for Ubuntu 14.04 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 (PUP-2568) Cannot use class references with upper cased strings
Title: Message Title
Kurt Wall commented on an issue
Re: Cannot use class references with upper cased strings
Verified at SHA=f3cf93a72fa04cfca39d55d129b5665990a52e7e:
# x.pp
include 'apache'
notice Class[Apache::Foo]
notice Class['Apache::Foo']
$a = 'Apache::Foo'
notice Class[$a]
# bundle exec puppet apply x.pp
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Notice: Scope(Class[main]): Class[Apache::Foo]
Notice: Scope(Class[main]): Class[Apache::Foo]
Notice: Scope(Class[main]): Class[Apache::Foo]
Notice: Compiled catalog for centos6-5-base.localdomain in environment production in 1.46 seconds
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 /root/puppet/lib/puppet/type.rb:816:in `set_default')
Notice: Finished catalog run in 1.20 seconds
Add Comment
Puppet / PUP-2568
Cannot use class references with upper cased strings
The future parser accepts {{Class[Apache::Foo]}} as a reference but will reject {{Class['Apache::Foo']}} and {{$a = 'Apache::Foo'; Class[$a]}} (a string or an _expression_ that results in a string. All of these variations should continue to work.
This message was sent by Atlassian JIRA
Jira (PUP-2182) Package resource not working as expected in 3.5.0
Title: Message Title
Joshua Cooper commented on an issue
Re: Package resource not working as expected in 3.5.0
On Centos 5.6, whose package provider supports virtual packages, with repo config pl-puppet-0dc5ad3da230fafb0fdd68b2e633b47fa333e742.
1. If allow_virtual is not specified, it issues a deprecation warning and says it failed to install the vim package (as expected), but actually it did install the package:
[root@centos64-x64 ~]# which vim
/usr/bin/which: no vim in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
[root@centos64-x64 ~]# puppet apply -e package { 'vim': ensure = latest } --debug
Debug: Executing '/bin/rpm --version'
Debug: Executing '/bin/rpm --version'
Debug: Executing '/bin/rpm -ql rpm'
...
Notice: Compiled catalog for centos64-x64.localdomain in environment production in 0.21 seconds
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')
...
Debug: Prefetching yum resources for package
Debug: Executing '/bin/rpm --version'
Debug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''
Debug: Executing '/bin/rpm -q vim --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
Debug: Package[vim](provider=yum): Ensuring = latest
Debug: Executing '/usr/bin/yum -d 0 -e 0 -y install vim'
Debug: Executing '/bin/rpm -q vim --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
Error: Could not update: Could not find package vim
Wrapped exception:
Could not find package vim
Error: /Stage[main]/Main/Package[vim]/ensure: change from absent to latest failed: Could not update: Could not find package vim
...
[root@centos64-x64 ~]# which vim
/usr/bin/vim
2. If allow_virtual = false, the deprecation warning is not displayed (as expected), but the package is still installed like above:
[root@centos64-x64 ~]# which vim
/usr/bin/which: no vim in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
# puppet apply -e package { 'vim': ensure = latest, allow_virtual = false }
...
Error: /Stage[main]/Main/Package[vim]/ensure: change from absent to latest failed: Could not update: Could not find package vim
...
[root@centos64-x64 ~]# which vim
/usr/bin/vim
3. If allow_virtual = true, it doesn't issue deprecation warning and successfully installs package (as expected):
[root@centos64-x64 ~]# which vim
/usr/bin/which: no vim in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
[root@centos64-x64 ~]# puppet apply -e package { 'vim': ensure = latest, allow_virtual = true }
Notice: Compiled catalog for centos64-x64.localdomain in environment production in 0.21 seconds
Notice: /Stage[main]/Main/Package[vim]/ensure: created
Notice: Finished catalog run in 1.66 seconds
[root@centos64-x64 ~]# which vim
/usr/bin/vim
Jira (PUP-854) Support Publishing NTFS ACL module to the forge
Title: Message Title Joshua Cooper assigned an issue to Peter Huene Puppet / PUP-854 Support Publishing NTFS ACL module to the forge Change By: Joshua Cooper Assignee: RobReynolds PeterHuene 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-1894) Cannot render EPP templates from a module
Title: Message Title
Joshua Partlow commented on an issue
Re: Cannot render EPP templates from a module
Merged to master in 71fbf00
Add Comment
Puppet / PUP-1894
Cannot render EPP templates from a module
According to the [module guide section about templates|http://docs.puppetlabs.com/puppet/latest/reference/modules_fundamentals.html#templates] a template is found in a module's template directory by joining the module name with the template name. However the {{epp}} function doesn't seem to be able to do this. It also does not find the template if the mod...
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-854) Support Publishing NTFS ACL module to the forge
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-854 Support Publishing NTFS ACL module to the forge Change By: Rob Reynolds Summary: Publish SupportPublishing NTFSACLmoduletotheforge 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-854) Support Publishing NTFS ACL module to the forge
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-854 Support Publishing NTFS ACL module to the forge Change By: Joshua Cooper Assignee: PeterHuene 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-2182) Package resource not working as expected in 3.5.0
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2182 Package resource not working as expected in 3.5.0 Change By: Joshua Cooper Assignee: JoshuaCooper PeterHuene 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-2581) Interpolated variables with leading underscore regression
Title: Message Title
Ethan Brown commented on an issue
Re: Interpolated variables with leading underscore regression
Verified in master
C:\source\puppet [master +3 ~0 -0 !] git reset --hard 38d6295 HEAD is now at 38d6295 Merge remote-tracking branch 'upstream/stable'
C:\source\puppet [master +3 ~0 -0 !] bundle exec puppet apply --parser=current hello.pp Notice: Compiled catalog for vagrant-2008r2.localdomain in environment production in 0.05 seconds Notice: hello world Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world' Notice: Finished catalog run in 0.41 seconds
C:\source\puppet [master +3 ~0 -0 !] bundle exec puppet apply --parser=future hello.pp Notice: Compiled catalog for vagrant-2008r2.localdomain in environment production in 0.64 seconds Notice: hello world Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world' Notice: Finished catalog run in 0.41 seconds
Add Comment
Puppet / PUP-2581
Interpolated variables with leading underscore regression
{code} root@puppetmaster:~# cat test.pp $_foo = 1 notify { ${_foo}: } # With current parser root@puppetmaster:~# puppet apply --parser=current test.pp Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations (at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1071:in `each') Notice: Compiled...
Jira (PUP-2584) Spurious warnings when using multiple file sources
Title: Message Title
Joshua Partlow commented on an issue
Re: Spurious warnings when using multiple file sources
For FR, Kylo and I verified on stable, that this doesn't regress
PUP-2290
(so behavior on an agent run without a certificate, behavior on an agent run with a certificate, in both cases when requesting an environment that doesn't exist). We haven't checked the original file source issue, or any cases on master.
Add Comment
Puppet / PUP-2584
Spurious warnings when using multiple file sources
When a file resource uses multiple sources puppet issues a warning like (the example manifest and the warning are not intended to match in file names): {code} Warning: Find /production/file_metadata/modules/slurm/c12-8.ymir.cse.ucdavis.edu/slurm.sh?links=managesource_permissions=use resulted in 404 with the message: Not Found: Could not find file_metad...
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
Jira (PDB-678) Build PDB 2.0.0 packages for Ubuntu 14.04
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-678 Build PDB 2.0.0 packages for Ubuntu 14.04 Issue Type: Sub-task Assignee: Unassigned Created: 19/May/14 11:58 AM Fix Versions: 2.0.0 Priority: Normal Reporter: Kenneth Barber This means doing a release by doing a local modification for the build by someone in release. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-680) Release PDB 2.0.0 for Ubuntu 14.04
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-680 Release PDB 2.0.0 for Ubuntu 14.04 Issue Type: Sub-task Assignee: Unassigned Created: 19/May/14 12:00 PM Fix Versions: 2.0.0 Priority: Normal Reporter: Kenneth Barber Release the ubuntu 14.04 packages for PDB 2.0.0. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-679) Smoke test PDB 2.0.0 packages for Ubuntu 14.04
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-679 Smoke test PDB 2.0.0 packages for Ubuntu 14.04 Issue Type: Sub-task Assignee: Unassigned Created: 19/May/14 11:59 AM Fix Versions: 2.0.0 Priority: Normal Reporter: Kenneth Barber Smoke test on Ubuntu 14.04 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-681) Light Announcements for PDB 2.0.0 and Ubuntu 14.04
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-681 Light Announcements for PDB 2.0.0 and Ubuntu 14.04 Issue Type: Sub-task Assignee: Unassigned Created: 19/May/14 12:01 PM Priority: Normal Reporter: Kenneth Barber We should make a lighter announcement for the release of Ubuntu 14.04 packages for PDB 2.0.0. This means: Do a follow up to our original PDB 2.0.0 release stating that we now have packages for Ubuntu 14.04. Tweet it Put it on IRC Add Comment
Jira (PUP-2182) Package resource not working as expected in 3.5.0
Title: Message Title
Peter Huene commented on an issue
Re: Package resource not working as expected in 3.5.0
You're observing the original bug that was fixed by supporting virtual packages; that is to say, when installing a virtual package, yum installs the package successfully but the followup query to check if it installed doesn't find it. The solution to that issue is what caused the issue noted in this ticket. This fix regresses us to the pre-3.5.0 behavior while allowing people that want to install a virtual package a way to get puppet to work (allow_virtual = true).
Add Comment
Puppet / PUP-2182
Package resource not working as expected in 3.5.0
One of my modules has the following code: {code} package { 'inetd': ensure = absent; } {code} On the next Puppet run, Puppet tries to remove the xinetd package (debug output): {code} Debug: Executing '/bin/rpm -q inetd --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' Debug: Executing '/bin/rpm -q i...
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.
Jira (PUP-2581) Interpolated variables with leading underscore regression
Title: Message Title
Ethan Brown commented on an issue
Re: Interpolated variables with leading underscore regression
Verified in puppet-4
C:\source\puppet [master +3 ~0 -0 !] git reset --hard 8738d78 HEAD is now at 8738d78 Merge remote-tracking branch 'upstream/master' into puppet-4
C:\source\puppet [master +3 ~0 -0 !] bundle exec puppet apply --parser=current hello.pp Notice: Compiled catalog for vagrant-2008r2.localdomain in environment production in 0.05 seconds Notice: hello world Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world' Notice: Finished catalog run in 0.39 seconds
C:\source\puppet [master +3 ~0 -0 !] bundle exec puppet apply --parser=future hello.pp Notice: Compiled catalog for vagrant-2008r2.localdomain in environment production in 0.64 seconds Notice: hello world Notice: /Stage[main]/Main/Notify[hello world]/message: defined 'message' as 'hello world' Notice: Finished catalog run in 0.39 seconds
Add Comment
Puppet / PUP-2581
Interpolated variables with leading underscore regression
{code} root@puppetmaster:~# cat test.pp $_foo = 1 notify { ${_foo}: } # With current parser root@puppetmaster:~# puppet apply --parser=current test.pp Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations (at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1071:in `each') Notice: Compiled...
Jira (PDB-679) Smoke test PDB 2.0.0 packages for Ubuntu 14.04
Title: Message Title Kenneth Barber commented on an issue Re: Smoke test PDB 2.0.0 packages for Ubuntu 14.04 Packages are here: http://builds.puppetlabs.lan/puppetdb/2.0.0/ Add Comment PuppetDB / PDB-679 Smoke test PDB 2.0.0 packages for Ubuntu 14.04 Smoke test on Ubuntu 14.04 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-2612) Puppet regsubst function does not match backslashes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2612 Puppet regsubst function does not match backslashes Change By: Henrik Lindberg Summary: Puppet Split regsubst function fails doesnotmatchbackslashes 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-2612) Puppet Split function fails
Title: Message Title
Henrik Lindberg commented on an issue
Re: Puppet Split function fails
The issue here is that single quoted string did not use to support escaping an escape (with other problems as a consequence. Single string a double quoted string now behaves the same way wrt escapes (backslahes).
The problem you are seeing has nothing to do with the split function, it is the string that is being used as input to regsubst that is wrong. Change it to:
$ports_string = regsubst($ports_regex, '\\|', ',', 'G')
You need 3 backslashes in the resulting string used to construct the regexp if you want a regexp that replaces a sequence of one backslash followed by pipe (to be replaced with a comma). To get 3 backslashes in the string you need 6 backslashes in the source text string (which results in 3 backslashes in the internal string, which is what is used to construct the regexp).
I am updating the title of this issue to better reflect the problem (and closing with a won't fix as it works as intended).
Add Comment
Puppet / PUP-2612
Puppet Split function fails
{code} puppet apply --parser future --debug --verbose c:/site.pp $ports_regex = 80\\|443 $ports_string = regsubst($ports_regex, '\\\|', ',', 'G') notify{CP1 ${ports_string}:} $ports_array = split($ports_string, ',') notify{CP2 ${ports_array}:} each($ports_array) |$port| { notify{CP3 ${port}:} file {${port}: pat...
Jira (PUP-2612) Puppet regsubst function does not match backslashes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2612 Puppet regsubst function does not match backslashes Change By: Henrik Lindberg 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-2612) Puppet regsubst function does not match backslashes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2612 Puppet regsubst function does not match backslashes 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 (PDB-673) puppetdb installation ignores libexecdir on archlinux
Title: Message Title Niels Abspoel commented on an issue Re: puppetdb installation ignores libexecdir on archlinux Hi Kenneth, I found the fix for the problem building the puppetdb package on archlinux from tarball: step 1: I need to clean the ext/files and pkg directories, these contain the wrong puppetdb binaries: rake clean fatal: Not a git repository (or any parent up to mount point /home) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). Warning: Existing rake commands are untested on 2.1 currently supported rubies include 1.8 or 1.9 rm -rf ext/files pkg step 2: recreate the ext/files and pkg directories rake package:bootstrap fatal: Not a git repository (or any parent up to mount point /home) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). Warning: Existing rake commands are untested on 2.1 currently supported rubies include 1.8 or 1.9 cd ext Cloning into 'packaging'... remote: Reusing existing pack: 4049, done. remote: Total 4049 (delta 0), reused 0 (delta 0) Receiving objects: 100% (4049/4049), 1.10 MiB | 439.00 KiB/s, done. Resolving deltas: 100% (2004/2004), done. Checking connectivity... done. cd - and then I can run the normal installation rake install DESTDIR, etc. and the result is the right environment on Archlinux. Add Comment PuppetDB / PDB-673 puppetdb installation ignores libexecdir on archlinux
Jira (PDB-673) puppetdb installation ignores libexecdir on archlinux
Title: Message Title
Kenneth Barber commented on an issue
Re: puppetdb installation ignores libexecdir on archlinux
Niels Abspoel so you think the problem is with our tarball perhaps? Maybe we should clean before packaging it.
Add Comment
PuppetDB / PDB-673
puppetdb installation ignores libexecdir on archlinux
Building puppetdb package on archlinux with rake package:bootstrap rake install PARAMS_FILE= DESTDIR=${pkgdir} This provides /usr/bin/puppetdb which looks in libexec dir: /usr/libexec/puppetdb instead of /usr/lib/puppetdb. Archlinux doesn't have /usr/libexec. If I read correctly this should be set the the template task but it looks like this ...
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-2615) wrong dependency: puppet-common uninstallable
Title: Message Title Hadmut Danisch created an issue Puppet / PUP-2615 wrong dependency: puppet-common uninstallable Issue Type: Bug Affects Versions: 3.6.0 Assignee: Unassigned Created: 19/May/14 1:14 PM Priority: Normal Reporter: Hadmut Danisch Hi, I'm using the puppet-labs repository for Debian/Ubuntu. puppet-common (3.6.0-1puppetlabs1) is uninstallable since it depends on facter (= 1.7.0) The available version of facter is 1.6.18-1puppetlabs1, which does not meet this dependency. regards Add Comment
Jira (PDB-682) PR (969): Added case logic for sbin_dir - aboe76
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-682 PR (969): Added case logic for sbin_dir - aboe76 Issue Type: Task Assignee: Unassigned Created: 19/May/14 1:20 PM Labels: github Priority: Normal Reporter: gepetto-bot Added case logic for sbin_dir Author: Niels Abspoel Company: Github ID: aboe76 Pull Request 969 Discussion Pull Request 969 File Diff Pull Request Description Archlinux only has /usr/bin and this symlinks to /usr/sbin (webhooks-id: ed37e33a2d3ade7f8c9d3aa90660c7af)
Jira (PDB-682) PR (969): Added case logic for sbin_dir - aboe76
Title: Message Title gepetto-bot commented on an issue Re: PR (969): Added case logic for sbin_dir - aboe76 pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-682 PR (969): Added case logic for sbin_dir - aboe76 h2. Added case logic for sbin_dir * Author: Niels Abspoel * Company: * Github ID: [aboe76|https://github.com/aboe76] * [Pull Request 969 Discussion|https://github.com/puppetlabs/puppetdb/pull/969] * [Pull Request 969 File Diff|https://github.com/puppetlabs/puppetdb/pull/969/files] h2. Pull Request Description Archlinux only has /usr/bin a... 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-682) PR (969): Added case logic for sbin_dir - aboe76
Title: Message Title gepetto-bot commented on an issue Re: PR (969): Added case logic for sbin_dir - aboe76 pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-682 PR (969): Added case logic for sbin_dir - aboe76 h2. Added case logic for sbin_dir * Author: Niels Abspoel * Company: * Github ID: [aboe76|https://github.com/aboe76] * [Pull Request 969 Discussion|https://github.com/puppetlabs/puppetdb/pull/969] * [Pull Request 969 File Diff|https://github.com/puppetlabs/puppetdb/pull/969/files] h2. Pull Request Description Archlinux only has /usr/bin a... 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-682) PR (969): Added case logic for sbin_dir - aboe76
Title: Message Title gepetto-bot commented on an issue Re: PR (969): Added case logic for sbin_dir - aboe76 kbarber commented: @aboe76 if you target this at stable, we can include this in a 2.0.1 release if we do one. Master represents 2.1.0 at the moment. Add Comment PuppetDB / PDB-682 PR (969): Added case logic for sbin_dir - aboe76 h2. Added case logic for sbin_dir * Author: Niels Abspoel * Company: * Github ID: [aboe76|https://github.com/aboe76] * [Pull Request 969 Discussion|https://github.com/puppetlabs/puppetdb/pull/969] * [Pull Request 969 File Diff|https://github.com/puppetlabs/puppetdb/pull/969/files] h2. Pull Request Description Archlinux only has /usr/bin a... 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-1509) Add puppet yum provider retry operation
Title: Message Title Adrien Thebo commented on an issue Re: Add puppet yum provider retry operation Per the conversation in https://github.com/puppetlabs/puppet/pull/1691 (specifically https://github.com/puppetlabs/puppet/pull/1691#issuecomment-19792180) I don't think we want to move in this direction; Puppet shouldn't be responsible for remediating issues with yum mirrors. Add Comment Puppet / PUP-1509 Add puppet yum provider retry operation Without this feature, in case of Error 256 No more mirrors to try yum provider would have failed operation in progress which would cause, for example, wanted package installation failed and all dependencies skipped. This is a problem because yum should provide operation completion a better way, at least it should try to expire local cache and retry t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDB-682) PR (969): Added case logic for sbin_dir - aboe76
Title: Message Title gepetto-bot commented on an issue Re: PR (969): Added case logic for sbin_dir - aboe76 aboe76 commented: please add this to the stable target if possible. It is just a small adjustment, so I don't need to do much script fu during package building on Archlinux. I have the Archlinux Package for puppetdb almost fully functional only issue is @java_bin, that is different, but I'm still thinking about the logic here. 2014-05-19 22:22 GMT+02:00 Ken Barber notificati...@github.com: @aboe76 https://github.com/aboe76 if you target this at stable, we can include this in a 2.0.1 release if we do one. Master represents 2.1.0 at the moment. — Reply to this email directly or view it on GitHubhttps://github.com/puppetlabs/puppetdb/pull/969#issuecomment-43552976 . Add Comment PuppetDB / PDB-682 PR (969): Added case logic for sbin_dir - aboe76 h2. Added case logic for sbin_dir * Author: Niels Abspoel * Company: * Github ID: [aboe76|https://github.com/aboe76] * [Pull Request 969 Discussion|https://github.com/puppetlabs/puppetdb/pull/969] * [Pull Request 969 File Diff|https://github.com/puppetlabs/puppetdb/pull/969/files] h2. Pull Request Description Archlinux only has /usr/bin a... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-682) PR (969): Added case logic for sbin_dir - aboe76
Title: Message Title gepetto-bot commented on an issue Re: PR (969): Added case logic for sbin_dir - aboe76 kbarber commented: @aboe76 with Github you have to rebase this against stable (I can't do it, unless i do it manually - and that would ruin how we do tests) and you'll have to re-raise the pull request. Unfortunately this means closing it first, let me do that. Re-open when you're ready. Add Comment PuppetDB / PDB-682 PR (969): Added case logic for sbin_dir - aboe76 h2. Added case logic for sbin_dir * Author: Niels Abspoel * Company: * Github ID: [aboe76|https://github.com/aboe76] * [Pull Request 969 Discussion|https://github.com/puppetlabs/puppetdb/pull/969] * [Pull Request 969 File Diff|https://github.com/puppetlabs/puppetdb/pull/969/files] h2. Pull Request Description Archlinux only has /usr/bin a... 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
Jira (PDB-682) PR (969): Added case logic for sbin_dir - aboe76
Title: Message Title gepetto-bot commented on an issue Re: PR (969): Added case logic for sbin_dir - aboe76 Pull request Added case logic for sbin_dir has been closed. Add Comment PuppetDB / PDB-682 PR (969): Added case logic for sbin_dir - aboe76 h2. Added case logic for sbin_dir * Author: Niels Abspoel * Company: * Github ID: [aboe76|https://github.com/aboe76] * [Pull Request 969 Discussion|https://github.com/puppetlabs/puppetdb/pull/969] * [Pull Request 969 File Diff|https://github.com/puppetlabs/puppetdb/pull/969/files] h2. Pull Request Description Archlinux only has /usr/bin a... 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-2214) Many puppet commands fail when using a configured or requested directory environment that doesn't exist.
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2214 Many puppet commands fail when using a configured or requested directory environment that doesn't exist. Change By: Adrien Thebo 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 (PDB-682) PR (969): Added case logic for sbin_dir - aboe76
Title: Message Title gepetto-bot commented on an issue Re: PR (969): Added case logic for sbin_dir - aboe76 aboe76 commented: Will do but first I need to address some server issues... @work Op 19 mei 2014 22:37 schreef Ken Barber notificati...@github.com: @aboe76 https://github.com/aboe76 with Github you have to rebase this against stable (I can't do it, unless i do it manually - and that would ruin how we do tests) and you'll have to re-raise the pull request. Unfortunately this means closing it first, let me do that. Re-open when you're ready. — Reply to this email directly or view it on GitHubhttps://github.com/puppetlabs/puppetdb/pull/969#issuecomment-43554630 . Add Comment PuppetDB / PDB-682 PR (969): Added case logic for sbin_dir - aboe76 h2. Added case logic for sbin_dir * Author: Niels Abspoel * Company: * Github ID: [aboe76|https://github.com/aboe76] * [Pull Request 969 Discussion|https://github.com/puppetlabs/puppetdb/pull/969] * [Pull Request 969 File Diff|https://github.com/puppetlabs/puppetdb/pull/969/files] h2. Pull Request Description Archlinux only has /usr/bin a... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2182) Package resource not working as expected in 3.5.0
Title: Message Title
Peter Huene commented on an issue
Re: Package resource not working as expected in 3.5.0
So to make this behavior consistent, I've added a yum list command when allow_virtual = false or default which will error on virtual package names, but accept available or installed real package names. The fix is available in Pull Request 2672. I've also moved the rpm query we do to ensure the correct version was installed to occur only if ensure is a version string; it was unnecessary otherwise.
Add Comment
Puppet / PUP-2182
Package resource not working as expected in 3.5.0
One of my modules has the following code: {code} package { 'inetd': ensure = absent; } {code} On the next Puppet run, Puppet tries to remove the xinetd package (debug output): {code} Debug: Executing '/bin/rpm -q inetd --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' Debug: Executing '/bin/rpm -q i...
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
Jira (PUP-2612) Puppet regsubst function does not match backslashes
Title: Message Title
utrecht commented on an issue
Re: Puppet regsubst function does not match backslashes
Changed as suggested. The outcome is the same.
$ports_regex = 80\\|443
# $ports_string = regsubst($ports_regex, '\\\|', ',', 'G')
$ports_string = regsubst($ports_regex, '\\|', ',', 'G')
notify{CP1 ${ports_string}:}
$ports_array = split($ports_string, ',')
notify{CP2 ${ports_array}:}
each($ports_array) |$port| {
notify{CP3 ${port}:}
file {${port}:
path = c:/temp/puppettest/${port},
ensure = present;
}
}
c:\temppuppet apply --parser future C:\Users\...\Desktop\site.pp
Error: Invalid tag cp2 at C:/Users/.../Desktop/site.pp:8 on node ...
Error: Invalid tag cp2 at C:/Users/.../Desktop/site.pp:8 on node ...
Add Comment
Puppet / PUP-2612
Puppet regsubst function does not match backslashes
{code} puppet apply --parser future --debug --verbose c:/site.pp $ports_regex = 80\\|443 $ports_string = regsubst($ports_regex, '\\\|', ',', 'G') notify{CP1 ${ports_string}:} $ports_array = split($ports_string, ',') notify{CP2 ${ports_array}:} each($ports_array) |$port| { notify{CP3 ${port}:} file {${port}: pat...
Jira (PUP-2616) 'json' gem not available on mountain lion
Title: Message Title Dustin J. Mitchell created an issue Puppet / PUP-2616 'json' gem not available on mountain lion Issue Type: Bug Affects Versions: 3.6.0 Assignee: Unassigned Created: 19/May/14 2:31 PM Environment: OS X Mountain Lion Priority: Normal Reporter: Dustin J. Mitchell Unlike Lion or Mavericks, Mountain Lion appears not to include the 'json' gem: [r...@talos-mtnlion-r5-006.test.releng.scl3.mozilla.com ~]# irb require 'json' LoadError: no such file to load -- json from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require' from (irb):1 this means that puppet fails to load: [r...@talos-mtnlion-r5-006.test.releng.scl3.mozilla.com ~]# puppet /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such
Jira (PUP-2617) Remount does not work when changing NFS servers
Title: Message Title Aaron Whiteside created an issue Puppet / PUP-2617 Remount does not work when changing NFS servers Issue Type: Bug Affects Versions: 3.5.1 Assignee: Unassigned Created: 19/May/14 2:34 PM Priority: Normal Reporter: Aaron Whiteside I had to manually umount the directories in question, then manually run puppet agent and only then did it succeed in applying this change on NFS server. Notice: /Stage[main]/Wsgw::Base/Mount[/scratch/mqube/m5.deploy/web_shared]/device: device changed 'nanas2a.mobilemessenger.lan:/vol/q_wsgw_web_shared/web_shared' to '192.168.9.11:/export/q_wsgw_web_shared/web_shared' Debug: Flushing mount provider target /etc/fstab Debug: /Stage[main]/Wsgw::Base/Mount[/scratch/mqube/m5.deploy/web_shared]: The container Class[Wsgw::Base] will propagate my refresh event Info: /Stage[main]/Wsgw::Base/Mount[/scratch/mqube/m5.deploy/web_shared]: Scheduling refresh of Mount[/scratch/mqube/m5.deploy/web_shared] Info: Mount[/scratch/mqube/m5.deploy/web_shared](provider=parsed): Remounting Debug: Executing '/bin/mount -o remount /scratch/mqube/m5.deploy/web_shared' Error: /Stage[main]/Wsgw::Base/Mount[/scratch/mqube/m5.deploy/web_shared]: Failed to call refresh: Execution of '/bin/mount -o remount /scratch/mqube/m5.deploy/web_shared' returned 32: Error: /Stage[main]/Wsgw::Base/Mount[/scratch/mqube/m5.deploy/web_shared]: Execution of '/bin/mount -o remount /scratch/mqube/m5.deploy/web_shared' returned 32: Notice: /Stage[main]/Wsgw::Base/Mount[/scratch/mqube/m5.deploy/smq/bus-internal]/device: device changed 'nanas2a.mobilemessenger.lan:/vol/q_smq_businternal' to
Jira (PUP-2617) Remount does not work when changing NFS servers
Title: Message Title Aaron Whiteside updated an issue Puppet / PUP-2617 Remount does not work when changing NFS servers Change By: Aaron Whiteside Environment: CentOS6.5 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2214) Many puppet commands fail when using a configured or requested directory environment that doesn't exist.
Title: Message Title Adrien Thebo commented on an issue Re: Many puppet commands fail when using a configured or requested directory environment that doesn't exist. Functional review: puppet module install fails with a meaningful error message: [root@green puppet]# bundle exec puppet module install branan/eight_hundred --environment nosuchluck --trace /platform/puppet/lib/puppet/application.rb:365:in `run': Could not find a directory environment named 'nosuchluck' anywhere in the path: /etc/puppet/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /platform/puppet/lib/puppet/util/command_line.rb:145:in `run' from /platform/puppet/lib/puppet/util/command_line.rb:91:in `execute' from /platform/puppet/bin/puppet:4 from /platform/puppet/.bundle/ruby/1.8/bin/puppet:19:in `load' from /platform/puppet/.bundle/ruby/1.8/bin/puppet:19 puppet parser validate fails to validate an environment when the given environment doesn't exist: [root@green puppet]# bundle exec puppet parser validate --environment nosuchluck /root/invalid-manifest.pp Error: Could not parse for environment nosuchluck: Syntax error at 'WHA' at /root/invalid-manifest.pp:1 [root@green puppet]# bundle exec puppet parser validate --environment nosuchluck /root/invalid-manifest.pp bundler: command not found: puppet Install missing gem executables with `bundle install` [root@green puppet]# bundle exec puppet parser validate --environment nosuchluck /root/invalid-manifest.pp /platform/puppet/lib/puppet/application.rb:365:in `run': Could not find a directory environment named 'nosuchluck' anywhere in the path: /etc/puppet/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /platform/puppet/lib/puppet/util/command_line.rb:145:in `run' from /platform/puppet/lib/puppet/util/command_line.rb:91:in `execute' from /platform/puppet/bin/puppet:4 from /platform/puppet/.bundle/ruby/1.8/bin/puppet:19:in `load' from /platform/puppet/.bundle/ruby/1.8/bin/puppet:19 Add Comment
Jira (PUP-2615) wrong dependency: puppet-common uninstallable
Title: Message Title Adrien Thebo commented on an issue Re: wrong dependency: puppet-common uninstallable Which Debian/Ubuntu release is this affecting? Add Comment Puppet / PUP-2615 wrong dependency: puppet-common uninstallable Hi, I'm using the puppet-labs repository for Debian/Ubuntu. puppet-common (3.6.0-1puppetlabs1) is uninstallable since it depends on facter (= 1.7.0) The available version of facter is 1.6.18-1puppetlabs1, which does not meet this dependency. regards 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-2610) Rack masters lose track of environment loaders
Title: Message Title
Peter Meier commented on an issue
Re: Rack masters lose track of environment loaders
This is quite a severe issue, because the catalog is then being compiled with a wrong environment, which means that stored configs being present from previous runs are being purged from the database, resulting in possible config changes across your whole infrastructure.
Add Comment
Puppet / PUP-2610
Rack masters lose track of environment loaders
When a puppet master is running under rack the first few seconds of running will cause it to use the wrong modules if the {{[main]}} section has a different {{modulepath}} (or {{environmentpath}}) from the {{[master]}} section. Reproduction: Given a rack master with the following puppet.conf: {code} [main] modulepath = /tmp/main-modules [master]...
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
Jira (PUP-2615) wrong dependency: puppet-common uninstallable
Title: Message Title Hadmut Danisch commented on an issue Re: wrong dependency: puppet-common uninstallable In my case Raspbian (Debian on Raspberry Pi) Add Comment Puppet / PUP-2615 wrong dependency: puppet-common uninstallable Hi, I'm using the puppet-labs repository for Debian/Ubuntu. puppet-common (3.6.0-1puppetlabs1) is uninstallable since it depends on facter (= 1.7.0) The available version of facter is 1.6.18-1puppetlabs1, which does not meet this dependency. regards 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-2616) 'json' gem not available on mountain lion
Title: Message Title
Nicholas Fagerlund commented on an issue
Re: 'json' gem not available on mountain lion
We currently list that as an extra step in the install instructions. http://docs.puppetlabs.com/guides/install_puppet/install_osx.html
Add Comment
Puppet / PUP-2616
'json' gem not available on mountain lion
Unlike Lion or Mavericks, Mountain Lion appears not to include the 'json' gem: {code} [r...@talos-mtnlion-r5-006.test.releng.scl3.mozilla.com ~]# irb require 'json' LoadError: no such file to load -- json from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' ...
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-2618) Unable to define multiple module paths when using directory environments
Title: Message Title Peter Meier created an issue Puppet / PUP-2618 Unable to define multiple module paths when using directory environments Issue Type: New Feature Affects Versions: 3.6.0 Assignee: Unassigned Created: 19/May/14 3:10 PM Priority: Normal Reporter: Peter Meier I have multiple modulepaths per environment. That's a way to structure your modules more by topic. Example: env/modules/topic1/module1 env/modules/topic1/module2 env/modules/topic2/module3 With the following config modulepath = $vardir/environments/$environment/modules/topic1:$vardir/environments/$environment/modules/topic2 To my understanding this is not possible with directory environments and which makes them not that usable for my environments. I have used the above pattern in several installations for example to serve group of modules from different repositories and so on. Add Comment
Jira (PUP-2615) wrong dependency: puppet-common uninstallable
Title: Message Title Adrien Thebo commented on an issue Re: wrong dependency: puppet-common uninstallable This looks like a duplicate of CPR-5 (https://tickets.puppetlabs.com/browse/CPR-5). Add Comment Puppet / PUP-2615 wrong dependency: puppet-common uninstallable Hi, I'm using the puppet-labs repository for Debian/Ubuntu. puppet-common (3.6.0-1puppetlabs1) is uninstallable since it depends on facter (= 1.7.0) The available version of facter is 1.6.18-1puppetlabs1, which does not meet this dependency. regards 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-2214) Many puppet commands fail when using a configured or requested directory environment that doesn't exist.
Title: Message Title
Adrien Thebo commented on an issue
Re: Many puppet commands fail when using a configured or requested directory environment that doesn't exist.
Joshua Partlow it looks like the puppet catalog face is seriously broken; what other FR would be appropriate for this issue?
Add Comment
Puppet / PUP-2214
Many puppet commands fail when using a configured or requested directory environment that doesn't exist.
This original description is documenting the difference between an agent making a request for an environment that does not exist, and an agent making a request for an environment that does not exist which also happens to be the configured environment on the master. On rhel6 vms, with a master puppet.conf of: {code} [main] # The Puppet log dire...
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-2615) wrong dependency: puppet-common uninstallable
Title: Message Title Hadmut Danisch commented on an issue Re: wrong dependency: puppet-common uninstallable No, it's a different problem. CPR-5 is about facter depending on dmidecode, which is not available on non-x86 architectures. This report is about puppet-common depending on a facter version that hasn't been release yet. Different problem. Seems as if you repo is sort of a mess... Add Comment Puppet / PUP-2615 wrong dependency: puppet-common uninstallable Hi, I'm using the puppet-labs repository for Debian/Ubuntu. puppet-common (3.6.0-1puppetlabs1) is uninstallable since it depends on facter (= 1.7.0) The available version of facter is 1.6.18-1puppetlabs1, which does not meet this dependency. regards 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
Jira (PUP-2582) Enable TLSv1.2 in apache vhost config
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2582 Enable TLSv1.2 in apache vhost config 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 (PUP-2182) Package resource not working as expected in 3.5.0
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Puppet / PUP-2182 Package resource not working as expected in 3.5.0 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-2619) Powershell provider is running a 32-bit PS on Win Server 2012 64-bit (puppet apply)
Title: Message Title
Dawn Foster commented on an issue
Re: Powershell provider is running a 32-bit PS on Win Server 2012 64-bit (puppet apply)
This was misfiled. I've moved it to the Puppet project.
Add Comment
Puppet / PUP-2619
Powershell provider is running a 32-bit PS on Win Server 2012 64-bit (puppet apply)
According to the documentation, the powershell provider is intended to run 64-bit ( despite ruby being 32-bit) For some reason when i exec the following it executes it against 32-bith1. This is my class: {code:title=os_config|borderStyle=solid} class os_config{ exec { 'install telnet client': command = '[IntPtr]::Size; Import-Module s...
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.
