Jira (PUP-9578) Remove distinction between `puppet parser validate` and `puppet parser validate --tasks`
Title: Message Title Reid Vandewiele commented on PUP-9578 Re: Remove distinction between `puppet parser validate` and `puppet parser validate --tasks` What does the user expect this command to do? From the built-in help: This action validates Puppet DSL syntax without compiling a catalog or syncing any resources. [...] As a user, I consider a plan to be Puppet DSL syntax just as much as I consider a desired-state manifest to be. While there is utility in making finer-grained validation available (such as are provided with the pdk validate command), I want a base syntax check to constrain itself to telling me if the content is valid Puppet DSL. Whether the content is valid for the purpose (based on e.g. if the name of the class or plan matches the modulename+filename, or if the plan or manifest is in a module-correct) is a higher level check. The puppet parser validate command allows syntax checking on stdin, communicating that file name and location is not fundamentally important to its purpose. The ask in this ticket is to make specification of purpose optional, or simply not part of this tool. This tool should consider a plan OR a manifest on stdin valid without the user needing to specify which is coming through. If the user chooses to specify, additional scrutiny can be applied. But if the user does not specify, a plan should not be reported as invalid syntax by default. > Your assumptions are not correct - there are functions that may work in either or both modes. I get that, but from a syntax and structure perspective (the value I want from this command), is it not possible to infer most anything we need to on that front based on what kind of block we're inside? E.g. in a plan block or in a class block, or not in a block at all. If not in a block, I would expect syntax validation to work for any function regardless of purpose. Syntax validation is not purpose validation. > if it detects automatically if it should validate in one more or the other - what was it the user intended? Per the above, I want an actual syntax validator that doesn't know about purpose. Purpose can certainly refine the check, but this ticket is asking for and asserting that it should not be necessary to know purpose to affirm that a file is valid DSL. It is only necessary to provide additional validation beyond that. Add Comment
Jira (PUP-9578) Remove distinction between `puppet parser validate` and `puppet parser validate --tasks`
Title: Message Title Henrik Lindberg commented on PUP-9578 Re: Remove distinction between `puppet parser validate` and `puppet parser validate --tasks` Your assumptions are not correct - there are functions that may work in either or both modes. Also, if it detects automatically if it should validate in one more or the other - what was it the user intended? What if you are validating something you think is a regular manifest and it has a plan in it? That is supposed to raise an error because it will not work if you intend to use that manifest for catalog compilation. (Obviously the vice versa applies). Are you looking for something that validates a bunch of manifests and switches mode depending on where the manifest is stored perhaps? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-495) Incorrect known_hosts checking
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-495 Incorrect known_hosts checking Change By: Melissa Amos Labels: customer0 docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1119) Improve Bolt startup time on Windows for bolt --help
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1119 Improve Bolt startup time on Windows for bolt --help Change By: Melissa Amos Labels: docs_reviewed windows Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9577) Large numbers of facts cause slow performance
Title: Message Title Henrik Lindberg commented on PUP-9577 Re: Large numbers of facts cause slow performance I suspect that # frozen_string_literal: true has an effect on number of allocations (Ruby compiler knows it can reuse one instance), but just calling freeze is not enough - that just takes time freezing an allocated object. Doubt Ruby is smart enough to optimize a "foo".freeze. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7138) debug output of sensitive resources or attributes thereof should be redacted
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-7138 debug output of sensitive resources or attributes thereof should be redacted Change By: Adam Bottchen CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-843) Generate a "retry" file when some nodes fail
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-843
Generate a "retry" file when some nodes fail
Change By:
Alex Dreyer
When a task/command/script/upload fails, Bolt should generate a {{retry}} file that includes the list of nodes that failed. That simplifies iterative workflows, whereby a user can try to run a task, make any needed adjustments on failed nodes, and then try it again.Questions:- What data goes in this file?- What is the interface for referencing failed nodes?- Can you reference the successful nodes too?- Is it overwritten by a successful action?- What happens when a plan fails? Possible defintion- File goes into /retry.json- Whenever any action fails or a plan returns with a resultset the file is overwritten- The format is an array where each item is the {{node}} and {{status}} from the Result's status hash. IE the actual result is not included.- This is accessed with a new targeting flag (like {{--query}}) {{--retry}} This has the possible values {{all}}, {{success}} or {{failure}} which filter on the {{status}} of the items in {{retry.json}}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9557) err: Could not request certificate: execution expired Exiting; failed to retrieve certificate and waitforcert is disabled
Title: Message Title Josh Cooper commented on PUP-9557 Re: err: Could not request certificate: execution expired Exiting; failed to retrieve certificate and waitforcert is disabled Nihaz Rhel5 will install an ancient version of puppet by default. You'll want to install a more recent version from https://puppet.com/docs/puppet/6.3/puppet_platform.html#task-383. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9557) err: Could not request certificate: execution expired Exiting; failed to retrieve certificate and waitforcert is disabled
Title: Message Title Josh Cooper assigned an issue to Nihaz Puppet / PUP-9557 err: Could not request certificate: execution expired Exiting; failed to retrieve certificate and waitforcert is disabled Change By: Josh Cooper Assignee: Nihaz Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-3674) confdir not set to /etc/puppet SSL Directories issue on config re-read
Title: Message Title Josh Cooper commented on PUP-3674 Re: confdir not set to /etc/puppet SSL Directories issue on config re-read This isn't reproducible for me, and is filed against an EOL agent (pre AIO). Closing. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1125) Add info about what was run to Result or ResultSet
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1125 Add info about what was run to Result or ResultSet Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-843) Generate a "retry" file when some nodes fail
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-843 Generate a "retry" file when some nodes fail Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9500) Puppet assumes client cert issuer is in the ca bundle downloaded from the server
Title: Message Title Josh Cooper commented on PUP-9500 Re: Puppet assumes client cert issuer is in the ca bundle downloaded from the server Updated PUP-9513 to deprecate settings. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9513) Deprecate SSL host, validators, indirected types and termini
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9513 Deprecate SSL host, validators, indirected types and termini Change By: Josh Cooper The following classes or methods should be deprecated in 6.x and removed in 7:* Puppet::Network::HttpPool.http_instance* Puppet::Network::HttpPool.http_ssl_instance* Puppet::SSL::HostIndirected Types* Puppet::SSL::Base* Puppet::SSL::Key* Puppet::SSL::Certificate* Puppet::SSL::CertificateRequest (just the indirector related stuff, the rest is ok)Termini* Puppet::Indirector::SslFile* Puppet::SSL::Key::** Puppet::SSL::Certificate::** Puppet::SSL::CertificateRequest::*Validators* Puppet::SSL::Validator* Puppet::SSL::Validator::** Puppet::SSL::VerifierAdapter Settings* ssl_client_ca_auth* ssl_server_ca_auth Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (BOLT-843) Generate a "retry" file when some nodes fail
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-843
Generate a "retry" file when some nodes fail
Change By:
Alex Dreyer
When a task/command/script/upload fails, Bolt should generate a {{retry}} file that includes the list of nodes that failed. That simplifies iterative workflows, whereby a user can try to run a task, make any needed adjustments on failed nodes, and then try it again. Questions:- What data goes in this file?- What is the interface for referencing failed nodes?- Can you reference the successful nodes too?- Is it overwritten by a successful action?- What happens when a plan fails?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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-1445) Certificate generation makes poor fingerprint digest alogrithm selection
Title: Message Title Josh Cooper commented on PUP-1445 Re: Certificate generation makes poor fingerprint digest alogrithm selection This issue has been overtaken by current events. puppet agent --fingerprint defaults to SHA256 (since 2012) in commit 4b96227da398016c9b39ed23bead127f0a9436fc The agent defaults to SHA256, SHA1, ... when signing its CSR The puppetserver-ca-cli uses the same logic when signing a cert The clojure CA always uses SHA256withRSA. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-2958) Rapid-fire puppet runs cause race condition with SSL data
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2958 Rapid-fire puppet runs cause race condition with SSL data Change By: Josh Cooper Fix Version/s: PUP 5.y Fix Version/s: PUP 6.y Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-953) Add file_upload support to BoltSpec
Title: Message Title
Cas Donoghue updated an issue
Puppet Task Runner / BOLT-953
Add file_upload support to BoltSpec
Change By:
Cas Donoghue
Release Notes Summary:
{{BoltSpec::Run}} now supports the {{upload_file}} action.
Release Notes:
Enhancement
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 (BOLT-953) Add file_upload support to BoltSpec
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-953 Add file_upload support to BoltSpec Change By: Cas Donoghue Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1198) Support capitals in aliases and group names
Title: Message Title Alex Dreyer commented on BOLT-1198 Re: Support capitals in aliases and group names Long term we don't expect a single inventory file to be adequate for bolt. The main proposal to fix this is an `inventory.d` directory that allows groups to be broken out into separate files. In the past we've had trouble with allowing capitals in objects that map to file names due to file system specific capitalization behavior. If we were going to support this I think we'd have to make group names and aliases case insensitive in bolt which is significantly more work than just changing the group and alias regex. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1198) Support capitals in aliases and group names
Title: Message Title Kevin Reeuwijk created an issue Puppet Task Runner / BOLT-1198 Support capitals in aliases and group names Issue Type: Improvement Affects Versions: BOLT 1.14.0, BOLT 1.13.1, BOLT 1.13.0, BOLT 1.12.0, BOLT 1.11.0, BOLT 1.10.0 Assignee: Unassigned Components: bolt Created: 2019/03/21 3:04 PM Priority: Normal Reporter: Kevin Reeuwijk Using one or more capitals in an alias or group name in inventory.yaml will result in strange behavior, it will complain about invalid group names, but not specify that capitals are the problem. Especially for Windows users, the usage of one/more/all capitals in these sorts of names is very normal. They are not aware there could be anything illegal with them. This also raises a separate concern about having case-sensitivity yes or no, if capitals were to be fully supported. Again, for Windows users, they are used to such things being case-insensitive. At the minimum, if Bolt wouldn't support capitals in any way going forward, a useful error message should be shown to the user, informing them that capitals can't be used.
Jira (PUP-9577) Large numbers of facts cause slow performance
Title: Message Title Brian Rak updated an issue Puppet / PUP-9577 Large numbers of facts cause slow performance Change By: Brian Rak Attachment: test3.patch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9577) Large numbers of facts cause slow performance
Title: Message Title Brian Rak commented on PUP-9577 Re: Large numbers of facts cause slow performance Allocations reduce significantly by applying fsl in more places, as well as caching the mangled version of names in scope.rb and templatewrapper.rb Down to Total allocated: 107510429 bytes (1298917 objects), which is a reduces the # of allocations by 41%... I suspect a lot of this is due to the repetition of names within the fact set. Horrible ruby patch in test3.patch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9499) Add Puppet::FileSystem#replace_file
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9499 Add Puppet::FileSystem#replace_file Change By: Josh Cooper Release Notes Summary: Adds a method Puppet::FileSystem.replace_file for atomically replacing a file , and modifies the SSL code to use it when saving keys and certs . If a mode is specified, it will always be applied to the file. Otherwise, if the file being replaced exists, it's mode will be preserved. If the file doesn't exist, then the mode will default to 0640. This method supersedes Puppet::Util.replace_file, and the latter will be deprecated in a future release. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9556) Add puppet ssl bootstrap action
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9556
Add puppet ssl bootstrap action
Change By:
Josh Cooper
Release Notes Summary:
Adds a "puppet ssl bootstrap" action that will perform the same SSL initialization that "puppet agent -t" does, but without the catalog application lifecycle (pluginsync, requesting a catalog, applying it, sending a report). The new action accepts the same {{-- onetime}} and {{-- waitforcert}} options option that {{puppet agent -t}} does. The former is useful so it doesn't To only run once and never wait indefinitely , specify a wait time of 0 . The latter is useful if you want to increase how frequently the agent polls for its certificate to be signed.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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-7903) Do not cache invalid node certificate from puppet master
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7903 Do not cache invalid node certificate from puppet master Change By: Josh Cooper Release Notes Summary: If a client cert, CA bundle or CRL bundle are invalid, then they will be discarded and not saved to disk , so the agent won't be stuck the next time it runs . Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1017) Inventory should warn when unexepected keys are at the top of a node or group object
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1017 Inventory should warn when unexepected keys are at the top of a node or group object Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9578) Remove distinction between `puppet parser validate` and `puppet parser validate --tasks`
Title: Message Title Reid Vandewiele created an issue Puppet / PUP-9578 Remove distinction between `puppet parser validate` and `puppet parser validate --tasks` Issue Type: Improvement Assignee: Unassigned Created: 2019/03/21 2:12 PM Priority: Normal Reporter: Reid Vandewiele Right now users need to manually indicate to the syntax validation command whether or not they will be passing in manifest data that uses plan features. puppet parser validate puppet parser validate --tasks Assertion: the only validation differences between these two commands can be automatically detected and set appropriately based on being in, or not being in, a plan block. Given the above assertion, we should remove the user burden of needing to indicate to puppet parser validate when plan code is input. Rather, the parser/validator should Do The Right Thing™ automatically. Eliminate the need to pass --tasks in any circumstance by auto-detecting plan blocks and validating inside them appropriately.
Jira (PUP-9494) Update HA Documentation on enabling a replica
Title: Message Title Melissa Amos commented on PUP-9494 Re: Update HA Documentation on enabling a replica Sebastian Miclea Bump^ Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9577) Large numbers of facts cause slow performance
Title: Message Title Brian Rak updated an issue Puppet / PUP-9577 Large numbers of facts cause slow performance Change By: Brian Rak Attachment: fsl.patch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9577) Large numbers of facts cause slow performance
Title: Message Title
Brian Rak commented on PUP-9577
Re: Large numbers of facts cause slow performance
I was reading through the memory profile, and noticed something weird: {{ 262822 "_"}} {{ 262337 /root/puppet/lib/puppet/parser/templatewrapper.rb:84}} This constant seems to get created hundreds of thousands of times, for no real reason... I enabled frozen_string_literal for this file (and scope.rb, which had a similar issue). This immediately reduced memory allocations during the benchmark by 13%. I don't know if this is going to break anything, but even so... freezing that one particular location seems like a really easy win.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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-2354) agent is confused about cert state
Title: Message Title Heston Hoffman updated an issue Puppet / PUP-2354 agent is confused about cert state Change By: Heston Hoffman Labels: redmine resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9437) Make it easier to set Puppets current locale
Title: Message Title Melissa Stone commented on PUP-9437 Re: Make it easier to set Puppets current locale Thomas Honey what's happened when you set `LANGAUGE` when using Litmus to test? How are test hosts set up for Litmus? Does the setup process install any required language/local packages? Can we assume that language support had already been installed for the language you want to test? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9569) Crontab prefetch fails when the filename is not a valid user
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9569 Crontab prefetch fails when the filename is not a valid user Change By: Jarret Lavallee Summary: Crontab error with prefetch fails when the filename begining with is not a hash valid user Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1197) Allow $nodes as second positional arg for run_plan()
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1197 Allow $nodes as second positional arg for run_plan() Change By: Nick Lewis Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1197) Allow $nodes as second positional arg for run_plan()
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1197 Allow $nodes as second positional arg for run_plan() Change By: Nick Lewis Team: Bolt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1197) Allow $nodes as second positional arg for run_plan()
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1197 Allow $nodes as second positional arg for run_plan() Change By: Nick Lewis Sprint: Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1197) Allow $nodes as second positional arg for run_plan()
Title: Message Title
Reid Vandewiele created an issue
Puppet Task Runner / BOLT-1197
Allow $nodes as second positional arg for run_plan()
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2019/03/21 11:57 AM
Priority:
Normal
Reporter:
Reid Vandewiele
To provide consistency of special treatment for a plan parameter named $nodes, allow the run_plan() function to be invoked with $nodes as the second positional argument, so that it can be used the same way run_task() is. Consider the following code:
run_task('util::change_password', $nodes,
username => 'Administrator',
password => 'puppetlabs',
)
run_plan('reboot', $nodes,
Jira (PUP-9437) Make it easier to set Puppets current locale
Title: Message Title Melissa Stone commented on PUP-9437 Re: Make it easier to set Puppets current locale Josh Cooper what do you mean using gettext-setup at runtime versus generating the pot files? I found https://confluence.puppetlabs.com/display/systemsEngineering/I18N+Testing+Puppet+Agent which has a lot of i18n details. Of specific interest: The variables in order of precedence is LANGUAGE takes precedence over LC_ALL LC_ALL takes precedence over LC_MESSAGES LC_MESSAGES takes precedence over LANG LANG Windows If above not set, then fall back to systems locale id (I.E what region/locale is the system set to) So, I can use the LANGUAGE env var to manage which language the locale gem passes to fast_gettext [0] Melissa@bubba:~/puppet:(master)$ be ./bin/puppet agent -t [258, 267] in /Users/Melissa/puppet/lib/puppet/gettext/config.rb 258: # Sets FastGettext's locale to the current system locale 259: def self.setup_locale 260: return if @gettext_disabled || !gettext_loaded? 261:
Jira (PUP-5389) PID race condition allows two puppet instances, which can result in failure to request certificate
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5389 PID race condition allows two puppet instances, which can result in failure to request certificate Change By: Josh Cooper Fix Version/s: PUP 5.y Fix Version/s: PUP 6.y Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-5389) PID race condition allows two puppet instances, which can result in failure to request certificate
Title: Message Title Josh Cooper commented on PUP-5389 Re: PID race condition allows two puppet instances, which can result in failure to request certificate In 6.4 the window for the race is much smaller (https://github.com/puppetlabs/puppet/blob/master/lib/puppet/ssl/state_machine.rb#L103-L116), but not eliminated. This is duplicated by PUP-9462. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9577) Large numbers of facts cause slow performance
Title: Message Title Brian Rak commented on PUP-9577 Re: Large numbers of facts cause slow performance Full GC log attached Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9577) Large numbers of facts cause slow performance
Title: Message Title Brian Rak updated an issue Puppet / PUP-9577 Large numbers of facts cause slow performance Change By: Brian Rak Attachment: 2019-03-21_12-50-30-gc.log.0.current Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1196) bolt-inventory-pdb examples in public documentation are incorrect
Title: Message Title Garrett Guillotte updated an issue Puppet Task Runner / BOLT-1196 bolt-inventory-pdb examples in public documentation are incorrect Change By: Garrett Guillotte Summary: bolt-inventory-pdb examples in public documentation are incorrect Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1196) bolt-inventory-pdb examples are incorrect
Title: Message Title Garrett Guillotte updated an issue Puppet Task Runner / BOLT-1196 bolt-inventory-pdb examples are incorrect Change By: Garrett Guillotte Labels: bolt documentation Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1189) Predocs for simple plans
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1189 Predocs for simple plans Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1196) bolt-inventory-pdb examples are incorrect
Title: Message Title
Garrett Guillotte updated an issue
Puppet Task Runner / BOLT-1196
bolt-inventory-pdb examples are incorrect
Change By:
Garrett Guillotte
*Steps to reproduce*0) Install Bolt, Puppet Server, and PuppetDB (or install Bolt on a monolithic PE 2018.1+ master), and populate some nodes, especially one or more Windows nodes and one or more nodes with certnames that start with {{basil}}.1) Copy the example {{pdb.yaml}} in the "File format" section of [https://puppet.com/docs/bolt/latest/inventory_file_generating.html] into a {{pdb.yaml}} file:{code}query: "nodes[certname] {}"groups:- name: windowsquery: "inventory[certname] { facts.osfamily = 'windows' }"config:transport: winrm- name: basilquery: "nodes[certname] { certname ~ '^basil' }"{code}2) Generate an access token: {{puppet access login \ - \ -lifetime 1d}}3) Attempt to run the example command in the "Usage" section using this {{pdb.yaml}}:{code}bolt-inventory-pdb pdb.yaml -o ~/.puppetlabs/bolt/inventory.yaml{code}*Expected results*The {{pdb.yaml}} content is correctly formatted, and the command produces an {{inventory.yaml}} file containing, as described in the docs, "all nodes (added) to the top-level group, a Windows group configured to use the WinRM transport, and a basil group for nodes with basil in the certname."*Observed results*The {{pdb.yaml}} example is incorrectly formatted, resulting in an error:{code}[root@pe-201817-master centos]# /opt/puppetlabs/bolt/bin/bolt-inventory-pdb pdb.yaml -o ~/.puppetlabs/bolt/inventory.yamlError: (pdb.yaml): did not find expected key while parsing a block mapping at line 1 column 1{code}*Workaround*Fix the formatting in {{pdb.yaml}}:{code}---query: "nodes[certname] {}"groups:- name: windows query: "inventory[certname] { facts.osfamily = 'windows' }" config:transport: winrm- name: basil query: "nodes[certname] { certname ~ '^basil' }"{code}Re-running the command returned {{inventory.yaml}} output that I expected:{code}---query: nodes[certname] {}groups:- name: windows query: inventory[certname] { facts.osfamily = 'windows' } config:transport: winrm nodes: []- name: basil query: nodes[certname] { certname ~ '^basil' } nodes: []nodes:- pe-201817-master.platform9.puppet.net{code}*Problems with the workaround* - It's unclear and unexplained why one query is on node inventories ({{inventory[certname]}}) and the others are on {{nodes[certname]}}. - The documentation under "Configuration" states that "{{bolt-inventory-pdb}} requires the following file settings" and lists the {{ \ - \ -token-file}}, {{ \ - \ -cacert}}, and {{ \ - \ -url}} flags. But none of those flags are actually required if you're using RBAC and a valid RBAC token has been generated to the default {{~/.puppetlabs/token}} path. - The example command beneath the list of "required" flags assumes a non-standard token path. - If the token is expired, or if you're not using RBAC, the command might also require the {{ \ - \ -cert}} and {{ \ - \ -key}} options, which are in the command's {{ \ - \ -help}} output
Jira (BOLT-1196) bolt-inventory-pdb examples are incorrect
Title: Message Title
Garrett Guillotte updated an issue
Puppet Task Runner / BOLT-1196
bolt-inventory-pdb examples are incorrect
Change By:
Garrett Guillotte
*Steps to reproduce*0) Install Bolt, Puppet Server, and PuppetDB (or install Bolt on a monolithic PE 2018.1+ master), and populate some nodes, especially one or more Windows nodes and one or more nodes with certnames that start with {{basil}}.1) Copy the example {{pdb.yaml}} in the "File format" section of [https://puppet.com/docs/bolt/latest/inventory_file_generating.html] into a {{pdb.yaml}} file:{code}query: "nodes[certname] {}"groups:- name: windowsquery: "inventory[certname] { facts.osfamily = 'windows' }"config:transport: winrm- name: basilquery: "nodes[certname] { certname ~ '^basil' }"{code}2) Generate an access token: {{puppet access login \ - \ -lifetime 1d}}3) Attempt to run the example command in the "Usage" section using this {{pdb.yaml}}:{code}bolt-inventory-pdb pdb.yaml -o ~/.puppetlabs/bolt/inventory.yaml{code}*Expected results*The {{pdb.yaml}} content is correctly formatted, and the command produces an {{inventory.yaml}} file containing, as described in the docs, "all nodes (added) to the top-level group, a Windows group configured to use the WinRM transport, and a basil group for nodes with basil in the certname."*Observed results*The {{pdb.yaml}} example is incorrectly formatted, resulting in an error:{code}[root@pe-201817-master centos]# /opt/puppetlabs/bolt/bin/bolt-inventory-pdb pdb.yaml -o ~/.puppetlabs/bolt/inventory.yamlError: (pdb.yaml): did not find expected key while parsing a block mapping at line 1 column 1{code}*Workaround*Fix the formatting in {{pdb.yaml}}:{code}---query: "nodes[certname] {}"groups:- name: windows query: "inventory[certname] { facts.osfamily = 'windows' }" config:transport: winrm- name: basil query: "nodes[certname] { certname ~ '^basil' }"{code}Re-running the command returned {{inventory.yaml}} output that I expected:{code}---query: nodes[certname] {}groups:- name: windows query: inventory[certname] { facts.osfamily = 'windows' } config:transport: winrm nodes: []- name: basil query: nodes[certname] { certname ~ '^basil' } nodes: []nodes:- pe-201817-master.platform9.puppet.net{code}*Problems with the workaround* - It's unclear and unexplained why one query is on node inventories ({{inventory[certname]}}) and the others are on {{nodes[certname]}}. - The documentation under "Configuration" states that "{{bolt-inventory-pdb}} requires the following file settings" and lists the {{ \ - \ -token-file}}, {{ \ - \ -cacert}}, and {{ \ - \ -url}} flags. But none of those flags are actually required if you're using RBAC and a valid RBAC token has been generated to the default {{~/.puppetlabs/token}} path. - The example command beneath the list of "required" flags assumes a non-standard token path. - If the token is expired, or if you're not using RBAC, the command might also require the {{ \ - \ -cert}} and {{ \ - \ -key}} options, which are in the command's {{--help}} output but
Jira (BOLT-1196) bolt-inventory-pdb examples are incorrect
Title: Message Title
Garrett Guillotte updated an issue
Puppet Task Runner / BOLT-1196
bolt-inventory-pdb examples are incorrect
Change By:
Garrett Guillotte
*Steps to reproduce*0) Install Bolt, Puppet Server, and PuppetDB (or install Bolt on a monolithic PE 2018.1+ master), and populate some nodes, especially one or more Windows nodes and one or more nodes with certnames that start with {{basil}}.1) Copy the example {{pdb.yaml}} in the "File format" section of [https://puppet.com/docs/bolt/latest/inventory_file_generating.html] into a {{pdb.yaml}} file:{code}query: "nodes[certname] {}"groups:- name: windowsquery: "inventory[certname] { facts.osfamily = 'windows' }"config:transport: winrm- name: basilquery: "nodes[certname] { certname ~ '^basil' }"{code}2) Generate an access token: {{puppet access login \ - \ -lifetime 1d}}3) Attempt to run the example command in the "Usage" section using this {{pdb.yaml}}:{code}bolt-inventory-pdb pdb.yaml -o ~/.puppetlabs/bolt/inventory.yaml{code}*Expected results*The {{pdb.yaml}} content is correctly formatted, and the command produces an {{inventory.yaml}} file containing, as described in the docs, "all nodes (added) to the top-level group, a Windows group configured to use the WinRM transport, and a basil group for nodes with basil in the certname."*Observed results*The {{pdb.yaml}} example is incorrectly formatted, resulting in an error:{code}[root@pe-201817-master centos]# /opt/puppetlabs/bolt/bin/bolt-inventory-pdb pdb.yaml -o ~/.puppetlabs/bolt/inventory.yamlError: (pdb.yaml): did not find expected key while parsing a block mapping at line 1 column 1{code}*Workaround*Fix the formatting in {{pdb.yaml}}:{code}---query: "nodes[certname] {}"groups:- name: windows query: "inventory[certname] { facts.osfamily = 'windows' }" config:transport: winrm- name: basil query: "nodes[certname] { certname ~ '^basil' }"{code}Re-running the command returned {{inventory.yaml}} output that I expected:{code}---query: nodes[certname] {}groups:- name: windows query: inventory[certname] { facts.osfamily = 'windows' } config:transport: winrm nodes: []- name: basil query: nodes[certname] { certname ~ '^basil' } nodes: []nodes:- pe-201817-master.platform9.puppet.net{code}*Problems with the workaround* - It's unclear and unexplained why one query is on node inventories ({{inventory[certname]}}) and the others are on {{nodes[certname]}}. - The documentation under "Configuration" states that "{{bolt-inventory-pdb}} requires the following file settings" and lists the {{ \ - \ -token-file}}, {{ \ - \ -cacert}}, and {{ \ - \ -url}} flags. But none of those flags are actually required if you're using RBAC and a valid RBAC token has been generated to the default {{~/.puppetlabs/token}} path. - The example command beneath the list of "required" flags assumes a non-standard token path. - If the token is expired, or if you're not using RBAC, the command might also require the {{ \ - \ -cert}} and {{ \ - \ -key}} options, which are in the command's {{--help}} output but
Jira (BOLT-1196) bolt-inventory-pdb examples are incorrect
Title: Message Title
Garrett Guillotte updated an issue
Puppet Task Runner / BOLT-1196
bolt-inventory-pdb examples are incorrect
Change By:
Garrett Guillotte
*Steps to reproduce*0) Install Bolt, Puppet Server, and PuppetDB (or install Bolt on a monolithic PE 2018.1+ master), and populate some nodes, especially one or more Windows nodes and one or more nodes with certnames that start with {{basil}}.1) Copy the example {{pdb.yaml}} in the "File format" section of [https://puppet.com/docs/bolt/latest/inventory_file_generating.html] into a {{pdb.yaml}} file:{code}query: "nodes[certname] {}"groups:- name: windowsquery: "inventory[certname] { facts.osfamily = 'windows' }"config:transport: winrm- name: basilquery: "nodes[certname] { certname ~ '^basil' }"{code}2) Generate an access token: {{puppet access login \ - \ -lifetime 1d}}3) Attempt to run the example command in the "Usage" section using this {{pdb.yaml}}:{code}bolt-inventory-pdb pdb.yaml -o ~/.puppetlabs/bolt/inventory.yaml{code}*Expected results*The {{pdb.yaml}} content is correctly formatted, and the command produces an {{inventory.yaml}} file containing, as described in the docs, "all nodes (added) to the top-level group, a Windows group configured to use the WinRM transport, and a basil group for nodes with basil in the certname."*Observed results*The {{pdb.yaml}} example is incorrectly formatted, resulting in an error:{code}[root@pe-201817-master centos]# /opt/puppetlabs/bolt/bin/bolt-inventory-pdb pdb.yaml -o ~/.puppetlabs/bolt/inventory.yamlError: (pdb.yaml): did not find expected key while parsing a block mapping at line 1 column 1{code}*Workaround*Fix the formatting in {{pdb.yaml}}:{code}---query: "nodes[certname] {}"groups:- name: windows query: "inventory[certname] { facts.osfamily = 'windows' }" config:transport: winrm- name: basil query: "nodes[certname] { certname ~ '^basil' }"{code}Re-running the command returned {{inventory.yaml}} output that I expected:{code}---query: nodes[certname] {}groups:- name: windows query: inventory[certname] { facts.osfamily = 'windows' } config:transport: winrm nodes: []- name: basil query: nodes[certname] { certname ~ '^basil' } nodes: []nodes:- pe-201817-master.platform9.puppet.net{code}*Problems with the workaround* - It's unclear and unexplained why one query is on node inventories ({{inventory[certname]}}) and the others are on {{nodes[certname]}}. - The documentation under "Configuration" states that "{{bolt-inventory-pdb}} requires the following file settings" and lists the {{ \ - \ -token-file}}, {{ \ - \ -cacert}}, and {{ \ - \ -url}} flags. But none of those flags are actually required if you're using RBAC and a valid RBAC token has been generated to the default {{~/.puppetlabs/token}} path , and the . - The example command beneath the list of "required" flags assumes a non-standard token path and . - If the token is expired, or if you're not using RBAC, the command might also require the {{ \ - \ -cert}} and {{ \ - \ -key}} options, which are in the command's
Jira (BOLT-1052) Support run-as for shell localhost transport.
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1052 Support run-as for shell localhost transport. Change By: David Kramer Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9577) Large numbers of facts cause slow performance
Title: Message Title Brian Rak commented on PUP-9577 Re: Large numbers of facts cause slow performance So here's why I think this is memory related. I enabled GC logging on one of my puppet servers, and it certainly seems like it's generating 10GB of garbage every few seconds: 2019-03-21T12:52:07.675-0400: 97.148: [GC pause (G1 Evacuation Pause) (young) [Eden: 9672.0M(9672.0M)->0.0B(9392.0M) Survivors: 152.0M->208.0M Heap: 10.6G(24.0G)->1228.0M(24.0G)] 2019-03-21T12:52:18.699-0400: 108.172: [GC pause (G1 Evacuation Pause) (young) [Eden: 9392.0M(9392.0M)->0.0B(9336.0M) Survivors: 208.0M->208.0M Heap: 10.4G(24.0G)->1228.0M(24.0G)] 2019-03-21T12:52:30.695-0400: 120.167: [GC pause (G1 Evacuation Pause) (young) [Eden: 8864.0M(4232.0M)->0.0B(9376.0M) Survivors: 208.0M->240.0M Heap: 10092.0M(24.0G)->1260.0M(24.0G)] 2019-03-21T12:52:42.453-0400: 131.925: [GC pause (G1 Evacuation Pause) (young) [Eden: 9376.0M(9376.0M)->0.0B(9048.0M) Survivors: 240.0M->280.0M Heap: 10.4G(24.0G)->1300.0M(24.0G)] 2019-03-21T12:52:51.331-0400: 140.804: [GC pause (G1 Evacuation Pause) (young) [Eden: 9048.0M(9048.0M)->0.0B(9992.0M) Survivors: 280.0M->248.0M Heap: 10.1G(24.0G)->1268.0M(24.0G)] 2019-03-21T12:53:02.207-0400: 151.680: [GC pause (G1 Evacuation Pause) (young) [Eden: 9992.0M(9992.0M)->0.0B(8488.0M) Survivors: 248.0M->296.0M Heap: 11.0G(24.0G)->1316.0M(24.0G)] 2019-03-21T12:53:10.381-0400: 159.854: [GC pause (G1 Evacuation Pause) (young) [Eden: 8488.0M(8488.0M)->0.0B(7896.0M) Survivors: 296.0M->296.0M Heap: 9804.0M(24.0G)->1316.0M(24.0G)] 2019-03-21T12:53:17.530-0400: 167.003: [GC pause (G1 Evacuation Pause) (young) [Eden: 7896.0M(7896.0M)->0.0B(4008.0M) Survivors: 296.0M->304.0M Heap: 9212.0M(24.0G)->1320.0M(24.0G)] 2019-03-21T12:53:22.759-0400: 172.232: [GC pause (G1 Evacuation Pause) (young) [Eden: 4008.0M(4008.0M)->0.0B(4968.0M) Survivors: 304.0M->304.0M Heap: 5328.0M(24.0G)->1324.0M(24.0G)] 2019-03-21T12:53:26.655-0400: 176.127: [GC pause (G1 Evacuation Pause) (young) [Eden: 4968.0M(4968.0M)->0.0B(5272.0M) Survivors: 304.0M->320.0M Heap: 6292.0M(24.0G)->1336.0M(24.0G)] 2019-03-21T12:53:32.472-0400: 181.944: [GC pause (G1 Evacuation Pause) (young) [Eden: 5272.0M(5272.0M)->0.0B(5304.0M) Survivors: 320.0M->328.0M Heap: 6608.0M(24.0G)->1348.0M(24.0G)] Add Comment
Jira (PUP-8586) Feature related debug messages are confusing and generate too much spam
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8586 Feature related debug messages are confusing and generate too much spam Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8586) Feature related debug messages are confusing and generate too much spam
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8586 Feature related debug messages are confusing and generate too much spam Change By: Josh Cooper Fix Version/s: PUP 6.4.1 Fix Version/s: PUP 6.4.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-4270) Support a new "configure expiration" command
Title: Message Title Heston Hoffman commented on PDB-4270 Re: Support a new "configure expiration" command Thanks Rob Browning, I've linked to the doc from the release note Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1196) bolt-inventory-pdb examples are incorrect
Title: Message Title Melissa Amos moved an issue Puppet Task Runner / BOLT-1196 bolt-inventory-pdb examples are incorrect Change By: Melissa Amos Method Found: Customer Feedback Team: Bolt Workflow: Documentation Scrum Team Workflow Key: DOCUMENT BOLT - 987 1196 Project: Documentation Puppet Task Runner Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because
Jira (PUP-9437) Make it easier to set Puppets current locale
Title: Message Title Thomas Honey commented on PUP-9437 Re: Make it easier to set Puppets current locale +1 to what Josh Cooper is saying Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9577) Large numbers of facts cause slow performance
Title: Message Title Brian Rak updated an issue Puppet / PUP-9577 Large numbers of facts cause slow performance Change By: Brian Rak Attachment: facts.json Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-1189) Predocs for simple plans
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1189 Predocs for simple plans Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9577) Large numbers of facts cause slow performance
Title: Message Title
Brian Rak created an issue
Puppet / PUP-9577
Large numbers of facts cause slow performance
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
cpu_profiles.zip, heap_profiles.zip, mem_profile_6kfacts, mem_profile_defaultfacts
Created:
2019/03/21 8:24 AM
Priority:
Normal
Reporter:
Brian Rak
Puppet Version: mix of 5.58 and 6.3.0 Puppet Server Version: 6.2.1 OS Name/Version: CentOS 7 Many of our hosts have relatively large numbers of facts (~6k or so). We've been seeing performance issues on our masters that seem to be related to memory pressure, and believe these to be related to the fact count. I hacked up the full_catalog benchmark to use an exported copy of facts from our environment, and saw that catalog compilation times went up by 1.1s (about a 50% increase over the unmodified test). Looking at the memory profile, I see what appears to be a very significant increase in the number of objects allocated. Is this behavior expected? I wouldn't really expect 6k facts to cause such a dramatic increase here. I've attached a few things here:
mem_profile_defaultfacts -> Memory profile output from an unmodified full_catalog benchmark
mem_profile_6kfacts -> Memory profile output from the modified benchmark with a high fact count.
heap_profiles.zip -> Output from heap_dump benchmarks, named as above
cpu_profiles.zip -> Output from profile benchmarks
facts.json -> Sanitized version of our facts
I had just changed full_catalog/benchmarker.rb to have `facts = Puppet::Node::Facts.new("testing", JSON.parse(`cat /root/facts`))` ... my ruby skills
Jira (BOLT-1132) Environment variables do not propagate to actions run on localhost.
Title: Message Title Alex Dreyer commented on BOLT-1132 Re: Environment variables do not propagate to actions run on localhost. I can't replicate this issue. The puppetlabs-aws module is picking up authentication environment variables with `bolt apply` or an apply statement. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9554) Add ability to create regexp with all special chars escaped
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-9554 Add ability to create regexp with all special chars escaped Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-4270) Support a new "configure expiration" command
Title: Message Title Rob Browning commented on PDB-4270 Re: Support a new "configure expiration" command Heston Hoffman Yeah, should have mentioned that – if you look at the "git log -p" and search (typically via '/') for PDB-4270, you should jump to the commit including the doc changes. I suspect the likely entry point would be the summary in documentation/api/command/v1/commands.markdown, i.e. the ### "configure expiration", version 1 (experimental) section. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9576) Puppet Catalog Command
Title: Message Title
Patrick Grant created an issue
Puppet / PUP-9576
Puppet Catalog Command
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2019/03/21 6:13 AM
Priority:
Normal
Reporter:
Patrick Grant
Puppet Version: 5.5.6 Puppet Server Version: 5.3.5 OS Name/Version: RHEL 7.5 Issue raised on behalf of a customer: In the documentation, it says "Retrieve the catalog for a node" for the command 'puppet catalog find' When the customer runs this from their master, then they only get the catalog of the master with some changes so it looks like it would be a catalog from the node specified by . The commands used were
puppet catalog find --terminus rest --environment production node.domain.org
{{}}
puppet catalog find --terminus rest --server > agent-catalog.json
{{}} I think here we either need to be more clear in our docs on how to use this command properly or if there is an issue here with the functionality then this needs to be resolved.
Jira (PUP-9554) split should allow splitting by raw string
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-9554
split should allow splitting by raw string
Change By:
Henrik Lindberg
Original- Currently it is impossible to just pass a String to split and split by that string, for example:{{split($var,'.')}}won't work as the string is treated as regexp and is basically equivalent of {{split($var,/./)}}While for dot it is trivial to escape (altho still surprising considering that's not how split function usually works in other languages), for more complex strings it is annoying at best (as there is AFAIK no "regex escaping" function in puppet.My proposition is to either * Make strings do not act as regexp. Types are there for a reason, if someone wants to split by regexp they should pass a regexp as argument * Make strings be interpolated to regexp only when they start and end with / and have something inbetween (so {{split($var,"/./")}}) gets interpreted as regexp but {{split($var,"//")}} does not) UpdateBest course of action here is to add the ability to create a Regexp where all special characters are escaped. This is easily done by adding a flag to {{Regexp.new}}. Then, if the resulting string is needed (to be concatenated with other strings to form the final regexp), that can be achieved by using {{String.new(Regexp("...", true))}} - i.e. by converting the created escaped regexp to a String.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9554) Add ability to create regexp with all special chars escaped
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9554 Add ability to create regexp with all special chars escaped Change By: Henrik Lindberg Summary: split should allow splitting by raw string Add ability to create regexp with all special chars escaped Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9575) puppet apply error on file /bigtop-home/bigtop-deploy/puppet/manifests/modules/stdlib/spec/fixtures/test/manifests/base32.pp
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9575 puppet apply error on file /bigtop-home/bigtop-deploy/puppet/manifests/modules/stdlib/spec/fixtures/test/manifests/base32.pp Change By: Henrik Lindberg Component/s: Applications Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9575) puppet apply error on file /bigtop-home/bigtop-deploy/puppet/manifests/modules/stdlib/spec/fixtures/test/manifests/base32.pp
Title: Message Title Henrik Lindberg commented on PUP-9575 Re: puppet apply error on file /bigtop-home/bigtop-deploy/puppet/manifests/modules/stdlib/spec/fixtures/test/manifests/base32.pp Hanumanth Sastry This seems to be a local problem at your end with configuration and/or your logic/naming rather than an actual problem with Puppet. You will most likely get this solved by hopping onto the puppet slack channel where community members will help you figure out what is wrong. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9575) puppet apply error on file /bigtop-home/bigtop-deploy/puppet/manifests/modules/stdlib/spec/fixtures/test/manifests/base32.pp
Title: Message Title Hanumanth Sastry updated an issue Puppet / PUP-9575 puppet apply error on file /bigtop-home/bigtop-deploy/puppet/manifests/modules/stdlib/spec/fixtures/test/manifests/base32.pp Change By: Hanumanth Sastry Attachment: puppet_exec_log Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9575) puppet apply error on file /bigtop-home/bigtop-deploy/puppet/manifests/modules/stdlib/spec/fixtures/test/manifests/base32.pp
Title: Message Title Hanumanth Sastry created an issue Puppet / PUP-9575 puppet apply error on file /bigtop-home/bigtop-deploy/puppet/manifests/modules/stdlib/spec/fixtures/test/manifests/base32.pp Issue Type: Task Affects Versions: PUP 6.3.0 Assignee: Alex Dreyer Attachments: base32.pp Components: Applications Created: 2019/03/21 2:18 AM Environment: base32.pp Priority: Normal Reporter: Hanumanth Sastry Command used on ubuntu 18.04: $ puppet apply -d --modulepath="/bigtop-home/bigtop-deploy/puppet/modules:/etc/puppet/modules" /bigtop-home/bigtop-deploy/puppet/manifests --trace --verbose Evaluation Error: Resource type not found: Stdlib::Base32 (file: /bigtop-home/bigtop-deploy/puppet/manifests/modules/stdlib/spec/fixtures/test/manifests/base32.pp, line: 10, column: 2) on node bigdataspark stdlib version 5.2.0 is installed at: /bigtop-home/bigtop-deploy/puppet/manifests/modules/ puppet version: 6.3.0 Tried changing syntax at error line Stdlib::Base32 $value but get getting Evaluation error.
Jira (PUP-9566) Allow to send extra headers when requesting a catalog compilation
Title: Message Title Nacho Barrientos commented on PUP-9566 Re: Allow to send extra headers when requesting a catalog compilation I agree with David that in our case using headers is much more lightweight in terms of operational cost and maintenance. As he mentioned, we're planning on using an agent-generated header to give a "hint" to the load balancing layer and then verify on the backend that the node is actually authorised to make such request doing an RPC to a trusted source of information. Apart from the issue when changing the hostgroup, persuading the managers of the external CA to sign CSRs containing the extra header (that must be validated) might be a PITA for us. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9554) split should allow splitting by raw string
Title: Message Title Mariusz Gronczewski commented on PUP-9554 Re: split should allow splitting by raw string Oh, so that's it. We just recently migrated ~70k codebase from pre-new-parser P3 to P5... with some parts of codebase dating to 0.24) so my only real use of types were when constraining class arguments, didn't even knew that is a thing in Puppet. As for regexp modification, yes, that looks useful Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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.
