Jira (PUP-1546) Improve validation error message for hash/resource (future parser)
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-1546 Improve validation error message for hash/resource (future parser) Change By: Henrik Lindberg Assignee: Andy Parker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1546) Improve validation error message for hash/resource (future parser)
Title: Message Title
Henrik Lindberg commented on PUP-1546
Re: Improve validation error message for hash/resource (future parser)
The above faulty manifest now produced:
Error: This Name is not productive. A non productive construct may only be placed last in a block/sequence at /Users/henrik/git/puppet/foo.pp:1:1
Error: This Name is not productive. A non productive construct may only be placed last in a block/sequence at /Users/henrik/git/puppet/foo.pp:1:7
Since we added validation of expressions without side effects and made improvements to how resource expressions are identified in the grammar, the above example now looks as if it had been entered as
'clasf' 'bar' { }
and naturally, the two strings (i.e. the Name tokens referred to in the error message) are meaningless. While the error messages does not say "hey you probably wanted to say 'class'", the first error message should at least point the user to the clasf and it should be possible from there to figure out what is wrong.
Please open new tickets for other concrete error message improvements. The case described in this ticket does no longer occur, so I am closing this ticket as a won't fix.
Add Comment
Jira (PUP-1793) Cleanup, reduce, and improve stdlib based on new Puppet 4 features
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1793 Cleanup, reduce, and improve stdlib based on new Puppet 4 features Change By: Henrik Lindberg Scrum Team: Modules Signing this epic over to MODULES team. Please assigning it back to Language if this was wrong. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2166) Add type_of function
Title: Message Title Henrik Lindberg commented on PUP-2166 Re: Add type_of function The type_of function was added to stdlib in MODULES-1473 . Closing this issue as a duplicate of that as the implementation work was done there. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3358) conflict between reserved word "type" vs stdlib "type" function
Title: Message Title Henrik Lindberg commented on PUP-3358 Re: conflict between reserved word "type" vs stdlib "type" function Closed as a duplicate of MODULES-1473 where the issues with type keyword has been fixed in stdlib. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3002) Better report invalid resource attribute errors
Title: Message Title Henrik Lindberg commented on PUP-3002 Re: Better report invalid resource attribute errors Doh, the message is actually trying to say that it is the parameter called "hash" that is wrong. Simply changing the message to: Invalid parameter: 'hash' makes it clear that it is an invalid parameter name, not an invalid "parameter hash". Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2686) []= on nil while evaluating VirtualQuery in future parser
Title: Message Title Henrik Lindberg commented on PUP-2686 Re: []= on nil while evaluating VirtualQuery in future parser any new information on this ? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1124) PuppetDB high CPU usage
Title: Message Title
Anton Fomenko updated an issue
PuppetDB / PDB-1124
PuppetDB high CPU usage
Change By:
Anton Fomenko
Greetings,We faced into issues with PuppetDB PostgreSQL processes using all cores on our Puppet Master server (LA = 100 with 32 cores).This server have following components installed:1. puppet-server 3.7.3 (httpd with passenger)2. PuppetDB 2.2.2 with PostgreSQL 9.3This is master sever from master-slave PostgreSQL replication setup using PuppetDB database and read-database settings.Issues was solved by following this instruction:https://docs.puppetlabs.com/puppetdb/latest/trouble_kahadb_corruption.htmlon all PuppetDB nodes and repeated one more time in approximately a week.top was showing a lot of DELETE PostgreSQL queries.Following queries were in blocked state in PostgreSQL:{noformat}-[ RECORD 1 ]--+blocked_pid| 17367blocked_user | puppetdbblocking_pid | 14736blocking_user | puppetdbblocked_statement | UPDATE certnames SET deactivated=$1 WHERE name=$2 AND (deactivated<$3 OR deactivated IS NULL)blocking_statement | DELETE FROM fact_paths fp | WHERE fp.id in ( SELECT fp.id |FROM fact_paths fp | inner join fact_values fv on fp.id = fv.path_id | inner join facts f on fv.id = f.fact_value_id |WHERE fp.id in ( select fv.path_id from fact_values fv where fv.id in ($1,$2,$3,$4,$5) ) |GROUP BY fp.id |HAVING COUNT(fv.id) = 1)-[ RECORD 2 ]--+blocked_pid| 19100blocked_user | puppetdbblocking_pid | 11406blocking_user | puppetdbblocked_statement | UPDATE certnames SET deactivated=$1 WHERE name=$2 AND (deactivated<$3 OR deactivated IS NULL)blocking_statement | DELETE FROM fact_paths fp | WHERE fp.id in ( SELECT fp.id |FROM fact_paths fp | inner join fact_values fv on fp.id = fv.path_id | inner join facts f on fv.id = f.fact_value_id |WHERE fp.id in ( select fv.path_id from fact_values fv where fv.id in ($1,$2,$3,$4) ) |GROUP BY fp.id{noformat}{noformat}postgres 15706 0.0 0.0 1308216 3044 ?Ss Jan14 4:53 postgres: wal sen
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko updated an issue PuppetDB / PDB-1124 PuppetDB high CPU usage Change By: Anton Fomenko Attachment: Screen Shot 2015-01-19 at 19.42.06.png Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2735) unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters
Title: Message Title Henrik Lindberg commented on PUP-2735 Re: unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters Any luck with running your example with --parser=future on the master? or comments on my last comment above? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2811) Provide method for class masquerading
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-2811 Provide method for class masquerading Change By: Henrik Lindberg Assignee: Andy Parker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-184) Using 'ip addr' over ifconfig
Title: Message Title Kristyna Streitova commented on FACT-184 Re: Using 'ip addr' over ifconfig Sorry, I didn't realize you cannot access this bug. The problem is with interfaces with long names. Suppose we have an interface called "HelloHowAreYou": Creating interface with a long name: testuser@linux-ouro:~> sudo /sbin/tunctl -u testuser -t HelloHowAreYou Set 'HelloHowAreYou' persistent and owned by uid 1000 Now if "ifconfig" is used then facter gets a wrong (shortened) interface name "HelloHowA" testuser@linux-ouro:~> /sbin/ifconfig -a HelloHowA Link encap:Ethernet HWadr C2:8B:C6:D2:D9:4D VŠESMĚROVÉ_VYSÍLÁNÍ MULTICAST MTU:1500 Metrika:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 délka odchozí fronty:500 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) If "ip link" would be used then facter gets a full interface name "HelloHowAreYou" testuser@linux-ouro:~> ip link 4: HelloHowAreYou: mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 500 link/ether c2:8b:c6:d2:d9:4d brd ff:ff:ff:ff:ff:ff Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2935) De-serializing resource title hashes from PSON raises an error under Ruby 1.8.7
Title: Message Title Henrik Lindberg commented on PUP-2935 Re: De-serializing resource title hashes from PSON raises an error under Ruby 1.8.7 From 4.0.0 (and in future parser in 3x) it is illegal to set a title to anything other than a string, (or an array of strings). The result is: Evaluation Error: Illegal title type at index 0. Expected String, got Hash[String, String] Which is not a pretty error message as there is no reference to the source, there is at least now a check in place when a catalog is constructed from puppet language source. Directly feeding serialized catalogs produced via some other means is not a very good idea since these formats are intended for machine to machine communication where puppet is at both ends and they may thus lack in error handling / explanation of what is wrong etc. Also note that Ruby 1.8.7 is no longer supported from starting with Puppet 4.0.0. Closing this as won't fix, but will log a new ticket to improve the error message when using a title of the wrong type. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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. Vis
Jira (PUP-3002) Better report invalid resource attribute errors
Title: Message Title Thomas Hallgren commented on PUP-3002 Re: Better report invalid resource attribute errors Merged to master at cf6c4eb Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2974) Cannot turn off allow_virtual warning in puppet apply
Title: Message Title Henrik Lindberg commented on PUP-2974 Re: Cannot turn off allow_virtual warning in puppet apply As I understand the above the problem is in an external module where assumptions are made about how puppet works. Happy to help the author of that module if required, but I am closing this issue as a Won't fix. Thanks for reporting back that the problem was found to be "elsewhere". Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3002) Better report invalid resource attribute errors
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-3002 Better report invalid resource attribute errors Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3002) Better report invalid resource attribute errors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3002 Better report invalid resource attribute errors Change By: Henrik Lindberg Sprint: Language 2015-01-21 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3002) Better report invalid resource attribute errors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3002 Better report invalid resource attribute errors Change By: Henrik Lindberg Fix Version/s: PUP 4.x Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3002) Better report invalid resource attribute errors
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3002 Better report invalid resource attribute errors Change By: Henrik Lindberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3018) Puppet doesn't like to evaluate 'require => [ [], [] ],'
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-3018 Puppet doesn't like to evaluate 'require => [ [], [] ],' Change By: Henrik Lindberg Assignee: Andy Parker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3018) Puppet doesn't like to evaluate 'require => [ [], [] ],'
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3018 Puppet doesn't like to evaluate 'require => [ [], [] ],' Linking to the "reimplement the compiler" epic. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3018) Puppet doesn't like to evaluate 'require => [ [], [] ],'
Title: Message Title Henrik Lindberg commented on PUP-3018 Re: Puppet doesn't like to evaluate 'require => [ [], [] ],' As a work around, call flatten (puppetlabs standardlib) function before assigning to require. The current implementation is really odd since the flattening affects all attributes, not just require. Not sure we are going to be able to tackle this in a sensible way without large rewrites (which we are going to be doing post Puppet 4.0.0 anyway). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3028) Using templates (erb) with scoped variables starting with a number causes run time errors.
Title: Message Title Henrik Lindberg commented on PUP-3028 Re: Using templates (erb) with scoped variables starting with a number causes run time errors. Since variables starting with a digit, and that is not completely decimal (for the purpose of referencing a regular _expression_ match group), are no longer acceptable in the puppet language from 4.0.0 (and in 3x with future parser), there is really no need to do anything about this issue. The error is flagged long before it reaches the ERB logic and any transformation to instance variables. Do not see much value in fixing this for 3.7.4 regular parser/evaluator. Closing a won't fix. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3167) node namespaces override class namespaces if they happen to match
Title: Message Title Henrik Lindberg commented on PUP-3167 Re: node namespaces override class namespaces if they happen to match if so, the fix is to change Puppet::Resource::Type.name to: def name return @name unless @name.is_a?(Regexp) "__regexp__" + @name.source.downcase.gsub(/[^-\w:.]/,'').sub(/^\.+/,'') end Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it
Jira (PUP-3167) node namespaces override class namespaces if they happen to match
Title: Message Title Henrik Lindberg commented on PUP-3167 Re: node namespaces override class namespaces if they happen to match Eric Sorenson - thoughts? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3167) node namespaces override class namespaces if they happen to match
Title: Message Title Henrik Lindberg commented on PUP-3167 Re: node namespaces override class namespaces if they happen to match A node is represented as a instance of a Resource::Type of type :node The name of the node must internally be a valid name since it is used for tagging purposes The internal name is a transformation of the regular _expression_ used to match the node, where all special characters are removed, and an resulting initial sequence of dots are removed. The real problem is the munged artifical name of a node resource since it is highly ambiguous and can clash in several other ways with the rest of the information. Without a new runtime/different representation of "a node in the catalog" this is difficult to tackle. One suggestion is to simply change the name mapping to something that is less likely to clash. This was not realy possible in 3x where it was also possible to inherit from a node - since this is removed in 4x, the name can be any valid name. As an example, if the name is mapped as before but with the prefix _regexp_, the reported problem does not occur, and the output then becomes: Notice: Scope(Node[__regexp__foo]): one Is it worth fixing the problem this way? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko updated an issue PuppetDB / PDB-1124 PuppetDB high CPU usage Change By: Anton Fomenko Attachment: Screen Shot 2015-01-19 at 16.14.54.png Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3170) Cap integer and float sizes
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-3170 Cap integer and float sizes Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3167) node namespaces override class namespaces if they happen to match
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-3167 node namespaces override class namespaces if they happen to match Change By: Henrik Lindberg Assignee: Andy Parker Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1126) Create a shorthand URL for fetching factset for a node
Title: Message Title Erik Dalén created an issue PuppetDB / PDB-1126 Create a shorthand URL for fetching factset for a node Issue Type: New Feature Assignee: Unassigned Created: 2015/01/19 5:33 AM Priority: Normal Reporter: Erik Dalén It would be great if you could fetch the factset for a node using something like /v4/nodes//factset instead of needing to construct a query with ["=", "certname", ]. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3170) Cap integer and float sizes
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-3170
Cap integer and float sizes
Change By:
Henrik Lindberg
The language specification now (PUP-3133) says that Integer and Float becomes BigInteger are capped to signed 64 bit integer, and BigDecimal automatically 64 bit double precision floats (IEEE 754) . In reality this will not This used to be unspecified, and "just work since the rest of way Ruby works". There was also a misconception in how Ruby transitions between the infrastructure available fixed types and Big representations ( notably binary it simply does not do widening to Big for floating point). The cap is needed because neither serialization and formats nor Puppet DB can work efficiently (if at all ) encodes integers as 64 bit signed, and floats as IEEE 754 binary64 with values outside of the now specified range .We should change the specification to put this cap on the runtime size of Integers (error on under/overflow) .We should also update / verify that the type system does not accept Integer values that are BigInteger, and that Float should not accept BigDecimal unless , except possibly if those data types hold values that fit 64 bit signed and IEEE 754 binary64 respectively and can be transformed to the 64 bit variants .This also means that we should type check attribute and variable assignments since {{Any}} does not mean "any ruby type". This last step will may have performance implications.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this messag
Jira (PUP-3170) Cap integer and float sizes
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-3170 Cap integer and float sizes Change By: Henrik Lindberg Assignee: Andy Parker Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1125) PuppetDB terminus fetches unstructured facts instead of structured
Title: Message Title Erik Dalén created an issue PuppetDB / PDB-1125 PuppetDB terminus fetches unstructured facts instead of structured Issue Type: Bug Affects Versions: PDB 2.2.2, PDB 2.2.1, PDB 2.2.0 Assignee: Unassigned Created: 2015/01/19 5:12 AM Priority: Normal Reporter: Erik Dalén When fetching cached facts the facts terminus should fetch it using the v4 API to get the structured ones instead of fetching stringified facts using the v3 API. Add Comment
Jira (PUP-3133) Decide on the specification of Integer/Float runtime types
Title: Message Title Henrik Lindberg commented on PUP-3133 Re: Decide on the specification of Integer/Float runtime types Specification updated. Puppet Integer values are specified to be -2^63 to 2^63-1. Floating point values are 64 bit (a.k.a "double precision floating point"). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3133) Decide on the specification of Integer/Float runtime types
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-3133 Decide on the specification of Integer/Float runtime types Change By: Henrik Lindberg Assignee: Andy Parker Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1124) PuppetDB high CPU usage
Title: Message Title
Anton Fomenko updated an issue
PuppetDB / PDB-1124
PuppetDB high CPU usage
Change By:
Anton Fomenko
Greetings,We faced into issues with PuppetDB PostgreSQL processes using all cores on our Puppet Master server (LA = 100 with 32 cores).This server have following components installed:1. puppet-server 3.7.3 (httpd with passenger)2. PuppetDB 2.2.2 with PostgreSQL 9.3This is master sever from master-slave PostgreSQL replication setup using PuppetDB database and read-database settings.Issues was solved by following this instruction:https://docs.puppetlabs.com/puppetdb/latest/trouble_kahadb_corruption.htmlon all PuppetDB nodes and repeated one more time in approximately a week.top was showing a lot of DELETE PostgreSQL queries.Following queries were in blocked state in PostgreSQL:{noformat}-[ RECORD 1 ]--+blocked_pid| 17367blocked_user | puppetdbblocking_pid | 14736blocking_user | puppetdbblocked_statement | UPDATE certnames SET deactivated=$1 WHERE name=$2 AND (deactivated<$3 OR deactivated IS NULL)blocking_statement | DELETE FROM fact_paths fp | WHERE fp.id in ( SELECT fp.id |FROM fact_paths fp | inner join fact_values fv on fp.id = fv.path_id | inner join facts f on fv.id = f.fact_value_id |WHERE fp.id in ( select fv.path_id from fact_values fv where fv.id in ($1,$2,$3,$4,$5) ) |GROUP BY fp.id |HAVING COUNT(fv.id) = 1)-[ RECORD 2 ]--+blocked_pid| 19100blocked_user | puppetdbblocking_pid | 11406blocking_user | puppetdbblocked_statement | UPDATE certnames SET deactivated=$1 WHERE name=$2 AND (deactivated<$3 OR deactivated IS NULL)blocking_statement | DELETE FROM fact_paths fp | WHERE fp.id in ( SELECT fp.id |FROM fact_paths fp | inner join fact_values fv on fp.id = fv.path_id | inner join facts f on fv.id = f.fact_value_id |WHERE fp.id in ( select fv.path_id from fact_values fv where fv.id in ($1,$2,$3,$4) ) |GROUP BY fp.id{noformat} {noformat}postgres 15706 0.0 0.0 1308216 3044 ?Ss Jan14 4:53 postgres: wal se
Jira (PUP-3766) exec should set LC_ALL and LANG to C by default
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3766 exec should set LC_ALL and LANG to C by default Change By: Henrik Lindberg Scrum Team: Language Client Platform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3548) 4x function API's call_function cannot call a 3x function
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-3548 4x function API's call_function cannot call a 3x function Change By: Thomas Hallgren Sprint: Language 2015-01-21 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3548) 4x function API's call_function cannot call a 3x function
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-3548 4x function API's call_function cannot call a 3x function Change By: Thomas Hallgren Assignee: Andy Parker Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3786) Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter
Title: Message Title Thomas Hallgren commented on PUP-3786 Re: Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter Merged to master at 7db531d Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3458) autorequire from DSL
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-3458 autorequire from DSL Change By: Henrik Lindberg Assignee: Andy Parker Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3458) autorequire from DSL
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-3458 autorequire from DSL Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3786) Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter
Title: Message Title Thomas Hallgren commented on PUP-3786 Re: Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter Merged to stable at ff20b5f Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3786) Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-3786 Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3862) Ability to disable automatic hiera lookup of class parameters
Title: Message Title Jiri Horky created an issue Puppet / PUP-3862 Ability to disable automatic hiera lookup of class parameters Issue Type: New Feature Affects Versions: PUP 3.7.2 Assignee: Unassigned Components: Puppet Server Created: 2015/01/19 4:35 AM Priority: Normal Reporter: Jiri Horky Automatic parameter lookup of unspecified class parameters in Hiera is certainly a good thing for many, bot definetelly not for every one. For example, we see it as a little bit too automatic, where one does not easily see when the given parameter got from. Instead, we use explicit hiera calls within our "profile" classes, so it is visible which parameters are fetch from hiera, and (this is impotant), failure to resolve a value from hiera results in error, which is behavior which we want. If not, we can use default values or hiera_undef. With automatic lookup, is adds another level of complexity. The main reason why to be able to disable it is performance. We have fairly complex catalogs with hundrends of classes. Also, we have 3 hiera backends. Right now, automatic hiera lookups constitutes of about 2/3 of puppet execution time. This is about 40-60s for us now and it makes live with puppet less convinient than it could be.
Jira (PUP-3717) Log output of service restart commands
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3717 Log output of service restart commands Change By: Henrik Lindberg Scrum Team: Language Client Platform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3786) Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3786 Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter Change By: Henrik Lindberg Sprint: Language 2015-01-21 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3786) Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3786 Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter Change By: Henrik Lindberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3786) Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3786 Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter Change By: Henrik Lindberg Fix Version/s: PUP 3.7.4 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3835) Specify that variables are case sensitive
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3835 Specify that variables are case sensitive Change By: Henrik Lindberg Fix Version/s: PUP 4.1.0 Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3814) Duplicated error output
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3814 Duplicated error output Change By: Henrik Lindberg Fix Version/s: PUP 4.1.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3814) Duplicated error output
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3814 Duplicated error output Change By: Henrik Lindberg Story Points: 2 1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3814) Duplicated error output
Title: Message Title Henrik Lindberg commented on PUP-3814 Re: Duplicated error output It is this line that causes the extra output: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/application/apply.rb#L241 It is problematic to simply remove it since the current logic rescues exceptions from both compilation (which handles its own logging) and the agent runtime (apply) which may not handle its own logging. A fix could use two being/rescue clauses where the first only handles compilation (without no logging), and the second could log as it currently does. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3766) exec should set LC_ALL and LANG to C by default
Title: Message Title Henrik Lindberg commented on PUP-3766 Re: exec should set LC_ALL and LANG to C by default Why is this a "Language" ticket? Is this for exec's performed by the master primarily, or for execs in providers (in which case this is a "Client Platform" ticket. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3835) Specify that variables are case sensitive
Title: Message Title
Henrik Lindberg commented on PUP-3835
Re: Specify that variables are case sensitive
Specification updated. A note also added stating that this may change in the future since it is inconsistent that the names of classes/defines are case insensitive but variables are not. (Variables have been case sensitive since way back in history...)
class foo($fredTheYak = 10) {
notice "fredTheYak => $fredTheYak"
notice "fredtheyak => $fredtheyak"
}
include foo
notice "foo::fredTheYak => $foo::fredTheYak"
notice "foo::fredtheyak = $foo::fredtheyak"
Produces
Notice: Scope(Class[Foo]): fredTheYak => 10
Notice: Scope(Cla
Jira (PUP-3859) Puppet Apply dependancy cycle error exits 0 (even on detailed exit codes)
Title: Message Title
Peter Souter commented on PUP-3859
Re: Puppet Apply dependancy cycle error exits 0 (even on detailed exit codes)
It's all around `puppet/lib/puppet/graph/relationship_graph.rb`, which raises the error:
def report_cycles_in_graph
cycles = find_cycles_in_graph
n = cycles.length # where is "pluralize"? --daniel 2011-01-22
return if n == 0
s = n == 1 ? '' : 's'
message = "Found #{n} dependency cycle#{s}:\n"
cycles.each do |cycle|
paths = paths_in_cycle(cycle)
message += paths.map{ |path| '(' + path.join(" => ") + ')'}.join("\n") + "\n"
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko created an issue PuppetDB / PDB-1124 PuppetDB high CPU usage Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2015-01-19 at 12.12.26.png Created: 2015/01/19 1:26 AM Priority: Normal Reporter: Anton Fomenko Greetings, We faced into issues with PuppetDB PostgreSQL processes using all cores on our Puppet Master server (LA = 100 with 32 cores). This server have following components installed: 1. puppet-server 3.7.3 (httpd with passenger) 2. PuppetDB 2.2.2 with PostgreSQL 9.3 This is master sever from master-slave PostgreSQL replication setup using PuppetDB database and read-database settings. Issues was solved by following this instruction: https://docs.puppetlabs.com/puppetdb/latest/trouble_kahadb_corruption.html on all PuppetDB nodes and repeated one more time in approximately a week. top was showing a lot of DELETE PostgreSQL queries. Following queries were in blocked state in PostgreSQL: -[ RECORD 1 ]--+--
