Jira (PUP-5647) Resource is stored by path and not by $name
Title: Message Title Bob van Bokkem commented on PUP-5647 Re: Resource is stored by path and not by $name My usecase is that i want to update the symlink in case of a new version of the software. This will be installed next to to current version. And i want a generic symlink that always points to the latest version. I don't understand why you want to check on the link for uniqueness. If the title itself needs to be unique. I choose for this myself. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5681) Resurrect benchmark rake tasks
Title: Message Title Josh Cooper created an issue Puppet / PUP-5681 Resurrect benchmark rake tasks Issue Type: Bug Assignee: Unassigned Created: 2016/01/08 10:11 AM Priority: Normal Reporter: Josh Cooper Puppet has a set of benchmarks that can be run via bundle exec rake benchmark:all:run, however, they do not work in puppet#stable, specifically this one fails: $ bundle exec rake benchmark:all:run ... rake benchmark:function_loading:run ...
Jira (PUP-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5659 Puppet master does not fail catalog on unexisting resource in resource parameter Change By: Julien Pivotto Comment: It is not a regression, it has always been like thishttps://travis-ci.org/roidelapluie/PUP-5659 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Josh Cooper commented on PUP-5209 Re: call_function and metadata.json: call a function from a different module, very strange behavior Since this issue only affects inter-module function calls and resolving module dependencies, I'm fine not backporting this. We may want to backport PUP-3121 though, because it breaks basic use cases like `puppet module install`. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5644) puppet lookup command creates new SSL hierarchy with self-signed CA
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-5644 puppet lookup command creates new SSL hierarchy with self-signed CA Change By: Sean Griffin Assignee: qa Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Julien Pivotto commented on PUP-5659 Re: Puppet master does not fail catalog on unexisting resource in resource parameter It is a regression between Puppet 3.4.0 and 3.5.0 https://travis-ci.org/roidelapluie/PUP-5659 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5659 Puppet master does not fail catalog on unexisting resource in resource parameter Change By: Julien Pivotto Comment: It is a regression between Puppet 3.4.0 and 3.5.0https://travis-ci.org/roidelapluie/PUP-5659 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2288) Use the historical-catalogs endpoint in export
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2288 Use the historical-catalogs endpoint in export Change By: Andrew Roetker Scope Change Category: Adopted Scope Change Reason: Had time, easy fix Sprint: PuppetDB 2016-01-13 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5623) Callable type should be able to describe return type
Title: Message Title
Peter Huene commented on PUP-5623
Re: Callable type should be able to describe return type
I think we're on the right track with the last Hash proposal. How would we handle capture and block parameters?
I envision something like this in the future, so I want to make sure we can represent it with the new Callable specification:
# Assuming there's some syntax for return type specification...
function foo($a, Integer $b = 0, String $c = something, *$d, Optional[Callable[1, 1]] $e) : Integer {
# yield to $e if it was passed, somehow...
$b
}
# Both these calls are acceptable
foo(bar) |$x| {
}
foo(bar)
Jira (PUP-5644) puppet lookup command creates new SSL hierarchy with self-signed CA
Title: Message Title Sean Griffin commented on PUP-5644 Re: puppet lookup command creates new SSL hierarchy with self-signed CA It appears that the new code fixes the server/agent use case (which is probably the more important of the two) but has no effect on the masterless use case. It is possible I don't understand the fail scenario. The description shows tracking of these certs in directory ~/.puppetlabs/. My runs generated no such directory. The new directory is in /etc/puppetlabs. Tested on centos-7 using the head of stable branch (which also includes the fix for PUP-5416 , puppet lookup command too verbose). Masterless use case: There appears to be no difference between the fixed and unfixed versions of puppet. In both cases a puppet-apply command or a puppet-lookup will result in new ssl directory containing certs, etc. being created in /etc/puppetlabs/puppet. Below is the result on the "fixed" version. # no ssl directory in /etc/puppetlabs/puppet. [root@bw7qlcliqg5a9qt ~]# cd /etc/puppetlabs/puppet [root@bw7qlcliqg5a9qt puppet]# ls auth.conf puppet.conf [root@bw7qlcliqg5a9qt puppet]# date Fri Jan 8 12:47:32 PST 2016
Jira (PDB-2311) Change command names to use `_` instead of `" "` or `-`
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2311 Change command names to use `_` instead of `" "` or `-` Change By: Andrew Roetker Summary: Change command names to use ` - _ ` instead of `" "` or `-` Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5623) Callable type should be able to describe return type
Title: Message Title
Henrik Lindberg commented on PUP-5623
Re: Callable type should be able to describe return type
One problem with that proposal is the use of Optional}}m it something different since it describes the ability to accept {{undef as a value, that is not the same at all as a missing value. Or to paraphrase: You can have a required parameter where undef is a valid value, as well as an optional parameter where undef is not allowed (and hence requires a default value _expression_ that results in a NotUndef value.
My proposal had parameters and optional_parameters separated for that reason. The other approach would be to require that the parameter's type is a hash (or tuple), if the parameter is something other than a required parameter. That could then be used for capture as well. We could perhaps also use enums as there are are only two values optional, and captures, and one combination optional_captures - I find it hard to name this parameter (some kind of type/kind, so maybe a Tuple? e.g.
Callable[{
params => {
a => Any,
b => [Integer, 'optional'],
c => [String, 'optional'],
d => [Any, 'capture', 'optional']
},
block => {
Jira (PUP-5623) Callable type should be able to describe return type
Title: Message Title
Peter Huene commented on PUP-5623
Re: Callable type should be able to describe return type
I'm not entirely opposed to having two different hashes, one for required and one for optional, but I'm not entirely convinced that we need to worry about potential user confusion for optional parameters that are of Optional type as it would probably be rare.
function foo(Optional[Integer] $x = 0) {
}
would simply be:
Callable[{ params => { x => Optional[Optional[Integer]] } }]
And using Optional like this has precedence: the hash passed to Struct uses it for semantic meaning for keys and not to express actual types.
On second thought, I think I like the two different lists better as it just makes it clearer at a glance what the actual parameter types are. The only benefit to having a single list would be one less thing for users to remember (required -> optional -> capture -> block) vs. (params -> capture -> block).
TL;DR: Fine with two lists.
Add Comment
Jira (PUP-5661) Stack level too deep issue
Title: Message Title
Henrik Lindberg commented on PUP-5661
Re: Stack level too deep issue
Ok, that locks like a normal "calling function" from a .pp file. Had this been an endless recursion problem, you would see the same sequence over and over at the end. What we can learn from that stacktrace is that it occurs on assignment to a variable eval_AssignmentExpression, and that it is set to the result of calling a function (the "with_block" does not say of this is a function call with a lambda or nor as it always takes that path.
Finding the name of the variable (inside the logic of eval_AssignmetExpression), or looking at the code that is evaluated in the eval_BlockExpression further down - to see more of where it is. This can be done by some more instrumentation of the code and installing a debugger. Then rather than dumping the stack, use {'require "byebug"}} sometime early in the source - say in Compiler::compile, and instead of dumping the stack on the exception, call debugger - once in the debugger, use up to move up to the interesting call frame. In the eval methods, there is always an AST object (typically named o that has information of value - like the position, and indirectly which .pp file it is - for something like the assingment _expression_, there are specific things like the variable name that can be obtained.
Probably, file and line is the most interesting - use Puppet::Pops::Utils.find_closest_positioned(o) to get an object that can give that information. Then call methods #to_uri() to get the file path, line and offset of the file.e.g. in the debugger use:
p Puppet::Pops::Utils.find_closest_positioned(o).to_uri()
You can then go and look at whats there to be able to form a hypotheses what caused a deep recursion.
Alternatively, since you are probably catching the out of stack exception is to throw another exception that puppet will decorate with information - say a ParseException (which in general is a really bad idea for things like out of stack and out of memory, but now you are doing this in a controlled experiment to find out what is causing the problem.
I hope this helps you - let me know if this is too technical and more help is needed.
Add Comment
Jira (PUP-5644) puppet lookup command creates new SSL hierarchy with self-signed CA
Title: Message Title Sean Griffin assigned an issue to Thomas Hallgren Have I misunderstood the masterless failing case? Is the fix for the server/agent use case sufficient to close this ticket? The masterless case doesn't generate the error message and it returns the correct value. Puppet / PUP-5644 puppet lookup command creates new SSL hierarchy with self-signed CA Change By: Sean Griffin Assignee: Sean Griffin Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Julien Pivotto commented on PUP-5659 Re: Puppet master does not fail catalog on unexisting resource in resource parameter It is not a regression, it has always been like this https://travis-ci.org/roidelapluie/PUP-5659 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2311) Change command names to use `-` instead of `" "`
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2311 Change command names to use `-` instead of `" "` Issue Type: Improvement Assignee: Unassigned Created: 2016/01/08 2:46 PM Fix Versions: PDB 4.0.0 Priority: Normal Reporter: Andrew Roetker Currently there's multiple back and forth between the command name with a space (e.g. "store report") and the version with a dash (e.g. "store-report"), we should just settle on the dashed version and get rid of the back and forth. Add Comment
Jira (PDB-2311) Change command names to use `_` instead of `" "` or `-`
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2311 Change command names to use `_` instead of `" "` or `-` Change By: Andrew Roetker Currently there's multiple back and forth between the command name with a space (e.g. "store report") and the version with a dash (e.g. "store-report"), we should just settle on the dashed an underscore version since this the command is going in the post params and get rid of the back and forth. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5644) puppet lookup command creates new SSL hierarchy with self-signed CA
Title: Message Title Jo Rhett commented on PUP-5644 Re: puppet lookup command creates new SSL hierarchy with self-signed CA Well one difference is that I was running as a non-root user, whereas you are not. Perhaps the code has differences in that situation? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5680) Ssh_authorized_key Unable to create directory
Title: Message Title
Patrick Goedhart created an issue
Puppet / PUP-5680
Ssh_authorized_key Unable to create directory
Issue Type:
Bug
Affects Versions:
PUP 3.7.3
Assignee:
Unassigned
Components:
Modules
Created:
2016/01/08 1:56 AM
Environment:
Sles 11.2 / Rhel 6.7
Priority:
Normal
Reporter:
Patrick Goedhart
I'm using module Ssh_authorized_key and this module is also using common.pp
define common::mkdir_p () {
Jira (PUP-5678) Dependency File [/etc/sudoers] has failures: true
Title: Message Title Patrick Goedhart created an issue Puppet / PUP-5678 Dependency File [/etc/sudoers] has failures: true Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Unassigned Components: Puppet Server Created: 2016/01/08 1:48 AM Environment: Sles 11.2 / Rhel 6.7 Priority: Normal Reporter: Patrick Goedhart Hi, I keep getting messages like: Jan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Sudo::Configs/Sudo::Conf[adm]/Exec[sudo-syntax-check for file /etc/sudoers.d/10_adm]) Dependency File[/etc/sudoers] has failures: true Jan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Sudo::Configs/Sudo::Conf[adm]/Exec[sudo-syntax-check for file /etc/sudoers.d/10_adm]) Dependency File[/etc/sudoers] has failures: true Jan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Sudo::Configs/Sudo::Conf[adm]/Exec[sudo-syntax-check for file /etc/sudoers.d/10_adm]) Skipping because of failed dependencies Jan 8
Jira (PUP-5679) Double entries in logfile
Title: Message Title Patrick Goedhart created an issue Puppet / PUP-5679 Double entries in logfile Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Unassigned Components: Puppet Server Created: 2016/01/08 1:49 AM Environment: Sles 11.2/Rhel 6.7 Priority: Normal Reporter: Patrick Goedhart In my logfiles I keep gettings double entries. e.g. Jan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Dependency File[/etc/pki/rpm-gpg/RPM-GPG-KEY-suse-release] has failures: true Jan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Dependency File[/etc/pki/rpm-gpg/RPM-GPG-KEY-suse-release] has failures: true Jan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Dependency File[/etc/zypp/repos.d/cak-base.repo] has failures: true Jan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Dependency File[/etc/zypp/repos.d/cak-base.repo] has failures: true Jan 8
Jira (PUP-5662) Update language spec reg. Hash data type being ordered
Title: Message Title Henrik Lindberg commented on PUP-5662 Re: Update language spec reg. Hash data type being ordered That would mean having two different kinds of hash runtime types - don't think we need that. It is fine to always use a hash that maintains the order in which keys were added add that the language instantiates them in "left to right" order. This constraint has nothing to do with the Hash type it is a quality of the runtime object use for instances of the type Hash. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5661) Stack level too deep issue
Title: Message Title Henrik Lindberg commented on PUP-5661 Re: Stack level too deep issue IIRC, the MRI stack can be set using ulimit (i.e. the "C stack"), there is no specific setting for MRI only that the default stacksize is on the small size for something like Ruby compared to C. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5647) Resource is stored by path and not by $name
Title: Message Title Henrik Lindberg commented on PUP-5647 Re: Resource is stored by path and not by $name I am now reading this report again and the example does not make sense since it specifies that the symlink /tmp/test should be both a link to /tmp/test122 and /tmp/test123 at the same time - that is exactly what the error is about - you cannot manage the same link twice. I am closing this as Incomplete, since there is nothing wrong with what puppet is doing. Suggest taking the issue to the email group to ask for advice how to best support the use case of "maintaining a link to latest version". Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5659) Puppet master does not fail catalog on unexisting resource in resource parameter
Title: Message Title Henrik Lindberg commented on PUP-5659 Re: Puppet master does not fail catalog on unexisting resource in resource parameter Not sure if this is a regression or not. Think we need to deal with this asap. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5679) Double entries in logfile
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5679 Double entries in logfile Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5661) Stack level too deep issue
Title: Message Title Henrik Lindberg commented on PUP-5661 Re: Stack level too deep issue If the cause is what I am guessing, the difference would be that there is already quite a lot on the stack when the master in production starts compilation. I have no idea how much that actually is, but you could get the same effect by reducing the amount of stack available when running master compile. You need to experiment... Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5661) Stack level too deep issue
Title: Message Title Matthew Fischer commented on PUP-5661 Re: Stack level too deep issue I just hacked it up again with puts caller so I'll get a stack now I hope. Probably 1-2 hours to repro. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5634) Application declaration "nodes" parameter should accept string representation of nodes, components
Title: Message Title David Lutterkort commented on PUP-5634 Re: Application declaration "nodes" parameter should accept string representation of nodes, components It's really something for J.D. Welch to look into./decide Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5662) Update language spec reg. Hash data type being ordered
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5662 Update language spec reg. Hash data type being ordered Change By: Henrik Lindberg Sprint: Language Triage 2016-01-13 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5591) undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-5591 undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class Change By: Ethan Brown Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5640) Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-5640 Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt Change By: Ethan Brown Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5661) Stack level too deep issue
Title: Message Title Matthew Fischer commented on PUP-5661 Re: Stack level too deep issue I just hacked up the code and had the ruby instantiator print out the typed_name and ruby_code_string, hoping to catch who was doing this. Had to run it for about an hour before it popped up. I should have guessed what I would see, but it looks like the ruby function instantiator is calling itself: Debug: Using cached facts for dnvrco02-control-002.os.cloud.twc.net Info: Caching node for dnvrco02-control-002.os.cloud.twc.net mfisch: function/hiera - require 'hiera/puppet_function' # Performs a standard priority lookup and returns the most specific value for a given key. # The returned value can be data of any type (strings, arrays, or hashes). # # The function can be called in one of three ways: # 1. Using 1 to 3 arguments where the arguments are:
Jira (PUP-5678) Dependency File [/etc/sudoers] has failures: true
Title: Message Title Henrik Lindberg commented on PUP-5678 Re: Dependency File [/etc/sudoers] has failures: true This looks like a problem when applying the catalog, not when compiling it. The problem looks to be reported by the agent. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5678) Dependency File [/etc/sudoers] has failures: true
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5678 Dependency File [/etc/sudoers] has failures: true Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5209) call_function and metadata.json: call a function from a different module, very strange behavior
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-5209 call_function and metadata.json: call a function from a different module, very strange behavior Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5661) Stack level too deep issue
Title: Message Title Matthew Fischer commented on PUP-5661 Re: Stack level too deep issue I ran compile in a tight loop all night generating 6G of logs. I was unable to reproduce it with just a compile although the regular catalog runs are generating it over night. Jan 8 06:34:56 dnvrco02-build-001 puppet-master[125124]: stack level too deep Jan 8 07:03:49 dnvrco02-build-001 puppet-master[134879]: stack level too deep Jan 8 07:57:39 dnvrco02-build-001 puppet-master[152992]: stack level too deep Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5679) Double entries in logfile
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5679
Double entries in logfile
Change By:
Henrik Lindberg
In my logfiles I keep gettings double entries. e.g. {code} Jan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Dependency File[/etc/pki/rpm-gpg/RPM-GPG-KEY-suse-release] has failures: trueJan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Dependency File[/etc/pki/rpm-gpg/RPM-GPG-KEY-suse-release] has failures: trueJan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Dependency File[/etc/zypp/repos.d/cak-base.repo] has failures: trueJan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Dependency File[/etc/zypp/repos.d/cak-base.repo] has failures: trueJan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Dependency File[/etc/pki/rpm-gpg/RPM-GPG-KEY-cak-release] has failures: trueJan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Dependency File[/etc/pki/rpm-gpg/RPM-GPG-KEY-cak-release] has failures: trueJan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Dependency File[/etc/pki/rpm-gpg/RPM-GPG-KEY-vmware-release] has failures: trueJan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Dependency File[/etc/pki/rpm-gpg/RPM-GPG-KEY-vmware-release] has failures: trueJan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Dependency File[/etc/zypp/repos.d/vmware-tools.repo] has failures: trueJan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Dependency File[/etc/zypp/repos.d/vmware-tools.repo] has failures: trueJan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Skipping because of failed dependenciesJan 8 09:10:20 clnortj1 puppet-agent[25950]: (/Stage[main]/Install/Package[netperf]) Skipping because of failed dependencies {code} Is there anyway to fix this?
Add Comment
