Jira (PUP-9640) Fix puppet user management on OS X 10.14
Title: Message Title Josh Cooper commented on PUP-9640 Re: Fix puppet user management on OS X 10.14 merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/e48d02630b1a19b3578915975387dcf5e700365c 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-9640) Fix puppet user management on OS X 10.14
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9640 Fix puppet user management on OS X 10.14 Change By: Josh Cooper Fix Version/s: PUP 6.0.9 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-9640) Fix puppet user management on OS X 10.14
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9640 Fix puppet user management on OS X 10.14 Change By: Josh Cooper Fix Version/s: PUP 6.0.8 Fix Version/s: PUP 5.5.13 Fix Version/s: PUP 5.5.14 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-9640) Fix puppet user management on OS X 10.14
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9640 Fix puppet user management on OS X 10.14 Change By: Josh Cooper Fix Version/s: PUP 6.0.8 Fix Version/s: PUP 5.5.13 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-273) Support noop from plans
Title: Message Title gustavo panizzo commented on BOLT-273 Re: Support noop from plans Alex Dreyer any chance to get this open again and in the roadmap? 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-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-9604 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression) 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 (PUP-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9604 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression) Change By: Jarret Lavallee Method Found: Needs Assessment Customer Feedback 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-4342) Support an option to update the timestamp used to expire nodes
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4342 Support an option to update the timestamp used to expire nodes Issue Type: Improvement Assignee: Unassigned Created: 2019/04/11 4:07 PM Priority: Normal Reporter: Zachary Kent Support a way for users to explicitly refresh the timestamp used for node TTL. This can be accomplished currently by repeatedly sending configure expiration commands for a node with expire.facts = true (see linked ticket for more detail) We should make this more explicit (maybe adding a new command) and look into the possibility of allowing bulk updates given a list of certnames. Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-1195) Generate a PP plan from a simple plan
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-1195 Generate a PP plan from a simple plan Change By: Lucy Wyman Assignee: Lucy Wyman 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-4341) Nodes which have only received "configure expiration" commands not present in inventory endpoint response
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4341 Nodes which have only received "configure expiration" commands not present in inventory endpoint response Issue Type: Improvement Assignee: Unassigned Created: 2019/04/11 3:54 PM Priority: Normal Reporter: Zachary Kent A node must have at least a factset/report/catalog for it to be present in the response from the inventory endpoint. With the addition of configure expiration commands nodes can now be created without submitting a factset/report/catalog. See if there is a way to have the existence of a node be sufficient for inclusion in the response from the inventory endpoint. The Console is currently submitting an empty factset to PDB (if none exist for a given certname) in order to work around nodes not being present in the PDB inventory endpoint. If unable to include nodes in the inventory endpoint without a factset, see if there is a way PDB could create an empty factset if none already exists when storing a configure expiration command. Add Comment
Jira (PUP-9637) Redacting Sensitive Data
Title: Message Title Josh Cooper commented on PUP-9637 Re: Redacting Sensitive Data Agree it should be on the list (as it's an obvious papercut for anyone trying to use Sensitive). But also we need to discuss the future of Sensitive and its cousin Encrypted. 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-9637) Redacting Sensitive Data
Title: Message Title Eric Thompson commented on PUP-9637 Re: Redacting Sensitive Data Josh Cooper is this big enough to nominate into the PM's tech-debt list for lovejoy timeframe? or should it be lumped in with other fixes? 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-4340) SPIKE: investigate improving reports / resource events table
Title: Message Title Robert Roland created an issue PuppetDB / PDB-4340 SPIKE: investigate improving reports / resource events table Issue Type: Story Assignee: Unassigned Components: PuppetDB Created: 2019/04/11 2:55 PM Priority: Normal Reporter: Robert Roland PE writes a "resources" column in the reports table that contains all resources (and events) during a puppet run, including changed and unchanged resources. In FOSS, this column is left empty. In both environments, the resource_events table contains a normalized version of the events from the reports. Investigate if these can be combined. This would reclaim storage space. Investigate if table partitioning can be used on the reports table. Add Comment
Jira (BOLT-1186) Improve Bolt startup time on Windows redux
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1186 Improve Bolt startup time on Windows redux Change By: Melissa Amos Labels: 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-1209) Intermittent AppVeyor test failure - WSMAN ERROR CODE: 1018 / WSMAN ERROR CODE: 2147746132
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1209 Intermittent AppVeyor test failure - WSMAN ERROR CODE: 1018 / WSMAN ERROR CODE: 2147746132 Change By: Melissa Amos Labels: 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-1242) run_as on localhost bugs
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1242 run_as on localhost bugs Change By: Melissa Amos Labels: 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-1209) Intermittent AppVeyor test failure - WSMAN ERROR CODE: 1018 / WSMAN ERROR CODE: 2147746132
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1209 Intermittent AppVeyor test failure - WSMAN ERROR CODE: 1018 / WSMAN ERROR CODE: 2147746132 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-1186) Improve Bolt startup time on Windows redux
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1186 Improve Bolt startup time on Windows redux Change By: Cas Donoghue Release Notes: Not Needed 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-1186) Improve Bolt startup time on Windows redux
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1186 Improve Bolt startup time on Windows redux 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-843) Generate a "rerun" file after every command
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-843
Generate a "rerun" file after every command
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 The file is overwritten after ever {{run}} command - 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}}) {{--rerun}} This has the possible values {{all}}, {{success}} or {{failure}} which filter on the {{status}} of the items in {{.rerun.json}}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-843) Generate a "rerun" file after every command
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-843
Generate a "rerun" file after every command
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 rerun }} This has the possible values {{all}}, {{success}} or {{failure}} which filter on the {{status}} of the items in {{ retry . rerun. json}}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-843) Generate a "rerun" file after every command
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-843 Generate a "rerun" file after every command Change By: Alex Dreyer Summary: Generate a " retry rerun " file when some nodes fail after every command 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 (PDOC-265) @example doesn't work with 4.x functions
Title: Message Title Jean Bond assigned an issue to Unassigned Puppet Strings / PDOC-265 @example doesn't work with 4.x functions Change By: Jean Bond Assignee: Jean Bond 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 (PDOC-265) @example doesn't work with 4.x functions
Title: Message Title Jean Bond commented on PDOC-265 Re: @example doesn't work with 4.x functions This does not appear to have fixed the issue with core docs generation. It may be a Strings thing or it may be an issue with the docs scripts. The function in Puppet code contains a lot of comment text that is seen in the 5.3 example (https://puppet.com/docs/puppet/5.3/function.html#regsubst) but is not showing up in the 6.4 generated docs (https://puppet.com/docs/puppet/6.4/function.html#regsubst). This includes, but is not limited to, the descriptions of the examples. When I generate docs, I get two files for functions: function_strings_prefer_v3.md: this contains the comment text and @example descriptions from the function. function_strings_prefer_v4.md: this... doesn't. It's the function_strings_prefer_v4.md file that becomes functions.html. I'm a little vague on what the difference is between the two files (Puppet 3 vs Puppet 4, I imagine?) because I'm still learning about how the generated docs work. Anyway, pinging Kris Bosland, as he's been helping recently on working out some of the bugs with generated docs. 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-1242) run_as on localhost bugs
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1242 run_as on localhost bugs 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-1242) run_as on localhost bugs
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1242 run_as on localhost bugs Change By: Cas Donoghue Release Notes: Not Needed 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-1194) Validate simple plans
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1194 Validate simple plans Change By: Cas Donoghue Assignee: Cas Donoghue 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-126) Support WinRM with Kerberos
Title: Message Title Sean Millichamp commented on BOLT-126 Re: Support WinRM with Kerberos Sorry forgot to include the link, the new PR is here: https://github.com/puppetlabs/bolt/pull/950 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-1133) Add bolt community slack to README, Contributing, and docs
Title: Message Title Lucy Wyman commented on BOLT-1133 Re: Add bolt community slack to README, Contributing, and docs Perfect! 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-1205) Only configure tasks to use Bolt's ruby interpreter for localhost
Title: Message Title Lucy Wyman commented on BOLT-1205 Re: Only configure tasks to use Bolt's ruby interpreter for localhost Look good! 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-1200) Localhost target should supply the puppet-agent feature
Title: Message Title Lucy Wyman commented on BOLT-1200 Re: Localhost target should supply the puppet-agent feature LGTM! 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-3750) (PDB 3654) bump version to 6.0.2
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3750 (PDB 3654) bump version to 6.0.2 Change By: Rob Browning Fix Version/s: PDB 6.0.2 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-1205) Only configure tasks to use Bolt's ruby interpreter for localhost
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1205 Only configure tasks to use Bolt's ruby interpreter for localhost Change By: Melissa Amos Labels: docs 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-126) Support WinRM with Kerberos
Title: Message Title Sean Millichamp commented on BOLT-126 Re: Support WinRM with Kerberos I put up a new PR based on Michael Smith's PR from January 2018 adjusted for the latest Bolt. It allows me to use a locally obtained Kerberos ticket on Linux to connect via WinRM with Kerberos to a target Windows system. I can confirm the inconsistent run results Michael Smith reported, I did a few sets of 100 runs and got approximately 10% failure. I understand the desire to not want to merge this when the behavior isn't consistent, but 10% failure is better than 100% failure. Also, I spent a while looking at this today and I believe it to be likely some error with the Kerberos decryption in WinRM. It seems to be similar to or the same as the issue here: https://github.com/WinRb/WinRM/issues/161 Open question: are we trying to enable transparent login from Windows nodes in a domain to other Windows nodes in that domain, or users getting a Kerberos ticket and using it to login to Windows domain nodes from heterogeneous sources? Those are going to be completely separate to implement. Our use case is we have a large number of completely disconnected domains with systems we need to WinRM into. Each domain has its own security policy and some of them only allow WinRM using Kerberos. 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
Jira (BOLT-1200) Localhost target should supply the puppet-agent feature
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1200 Localhost target should supply the puppet-agent feature Change By: Melissa Amos Labels: docs 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-1133) Add bolt community slack to README, Contributing, and docs
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1133 Add bolt community slack to README, Contributing, and docs Change By: Melissa Amos Labels: docs 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-1104) Linux implementation of the package task returns incorrect status output
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1104 Linux implementation of the package task returns incorrect status output Change By: Melissa Amos Labels: docs_reviewd 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-1104) Linux implementation of the package task returns incorrect status output
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1104 Linux implementation of the package task returns incorrect status output Change By: Melissa Amos Labels: docs_reviewd 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-1103) Linux implementation of the service task returns incorrect status output
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1103 Linux implementation of the service task returns incorrect status output Change By: Melissa Amos Labels: 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-1026) Bolt package should include hiera-eyaml
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1026 Bolt package should include hiera-eyaml Change By: Melissa Amos Labels: 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-1243) When a command is not specified on CLI a helpful error message is not raised
Title: Message Title
Cas Donoghue created an issue
Puppet Task Runner / BOLT-1243
When a command is not specified on CLI a helpful error message is not raised
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/04/11 12:46 PM
Priority:
Normal
Reporter:
Cas Donoghue
There appear to be inconsistencies with how we handle messaging about missing arguments on the CLI. For {plan,task,script} run nothing is attempted to be run and a helpful error message is returned if the object is empty. Similarly for file upload, and appy. However in the case of command run it appear that we try to connect and run nothing.
cas@cas-ThinkPad-T460p:~/working_dir/bolt/Boltdir$ bolt apply --rerun all
a manifest file or --execute is required
cas@cas-ThinkPad-T460p:~/working_dir/bolt/Boltdir$ bolt task run --rerun all
Must specify a task to run
cas@cas-ThinkPad-T460p:~/working_dir/bolt/Boltdir$ bolt script run --rerun all
Jira (PDB-4336) Check builds, promote to PE (PuppetDB 6.3.1)
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4336 Check builds, promote to PE (PuppetDB 6.3.1) Change By: Austin Blatt Assignee: Eric Thompson Austin Blatt 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-4335) Bump versions, push directly, and tag (PuppetDB 6.3.1)
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4335 Bump versions, push directly, and tag (PuppetDB 6.3.1) Change By: Austin Blatt Assignee: Eric Thompson Austin Blatt 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-4339) massive failures connecting to puppetdb
Title: Message Title Luis Ramirez commented on PDB-4339 Re: massive failures connecting to puppetdb Austin Blatt yes, you are correct, those names are anonymized . 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-4315) Handle resource-event duplicates in reports
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4315 Handle resource-event duplicates in reports Change By: Austin Blatt Team: PuppetDB 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-3742) Sync should skip records that are already present in the command queue
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3742 Sync should skip records that are already present in the command queue Change By: Zachary Kent Release Notes Summary: Allow PupppetDB to take already enqueued commands into accountwhen deciding which records need to by pulled from a remote PuppetDB during HA Sync. This fixes an issue where duplicate commands could be added to the command queue during sync, which could result in extra work and more downtime before the PuppetDB doing the sync could respond to new commands. 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-3742) Sync should skip records that are already present in the command queue
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3742 Sync should skip records that are already present in the command queue Change By: Zachary Kent Release Notes Summary: Allow PupppetDB to take already enqueued commands into account when deciding which records need to by pulled from a remote PuppetDB during HA Sync. This fixes an issue where duplicate commands could be added to the command queue during sync, which could result in extra work and more downtime before the PuppetDB doing the sync could respond to new commands. 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-4272) Update ha sync to handle explicit lifetime nodes
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4272 Update ha sync to handle explicit lifetime nodes Change By: Austin Blatt Team: PuppetDB 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-4321) Typo in blacklist configuration docs
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4321 Typo in blacklist configuration docs Change By: Austin Blatt Team: PuppetDB 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-4326) PuppetDB rejects catalogs with tags added automatically by Puppet
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4326 PuppetDB rejects catalogs with tags added automatically by Puppet Change By: Austin Blatt Team: PuppetDB 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-4339) massive failures connecting to puppetdb
Title: Message Title Austin Blatt commented on PDB-4339 Re: massive failures connecting to puppetdb Luis Ramirez did you anonymize that log message ie certname=HOSTNAME and 'server_urls': https://PUPPETDBHOSTNAME:8081? If not you're likely missing some configuration for communication between Puppet Server and PuppetDB. You can follow the docs here https://puppet.com/docs/puppetdb/6.3/connect_puppet_master.html 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-9627) Prepare JIRA and Confluence for release (Puppet Platform 6.4.1)
Title: Message Title Nirupama Mantha commented on PUP-9627 Re: Prepare JIRA and Confluence for release (Puppet Platform 6.4.1) Steps 1-6 are done. Fixed in Puppet Platform 6.4.1: https://tickets.puppetlabs.com/issues/?filter=32938 Introduced in Puppet Platform 6.4.1: https://tickets.puppetlabs.com/issues/?filter=32961 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-9628) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.1)
Title: Message Title Nirupama Mantha commented on PUP-9628 Re: Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.1) Steps 1-5 are done 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-9607) Prepare JIRA and Confluence for release (Puppet Platform 6.0.8)
Title: Message Title Nirupama Mantha commented on PUP-9607 Re: Prepare JIRA and Confluence for release (Puppet Platform 6.0.8) Steps 1-6 are done. Fixed in Puppet Platform 6.0.8: https://tickets.puppetlabs.com/issues/?filter=32939 Introduced in Puppet Platform 6.0.8: https://tickets.puppetlabs.com/issues/?filter=32964 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-9608) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.0.8)
Title: Message Title Nirupama Mantha commented on PUP-9608 Re: Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.0.8) Steps 1-5 are done 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-9591) Prepare JIRA and Confluence for release (Puppet Platform 5.5.13)
Title: Message Title Nirupama Mantha commented on PUP-9591 Re: Prepare JIRA and Confluence for release (Puppet Platform 5.5.13) steps 1-6 are done. Fixed in Puppet Platform 5.5.13: https://tickets.puppetlabs.com/issues/?filter=32936 Introduced in Puppet Platform 5.5.13: https://tickets.puppetlabs.com/issues/?filter=32967 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-3486) Update HakariCP to a more modern version than 2.4.3
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3486 Update HakariCP to a more modern version than 2.4.3 Change By: Rob Browning Fix Version/s: PDB 5.2.4 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-3742) Sync should skip records that are already present in the command queue
Title: Message Title Nirupama Mantha commented on PDB-3742 Re: Sync should skip records that are already present in the command queue Zachary Kent Can you update release notes for this? 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-4339) massive failures connecting to puppetdb
Title: Message Title luis commented on PDB-4339 Re: massive failures connecting to puppetdb Austin Blatt I have changed the loglevel for puppetdb since I was not getting any relevant error. Sadly I am not able to replicate the issue by myself, I will wait and try to catch when the errors show up 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-4174) Encoding issue submitting facts from package inventory
Title: Message Title Rob Browning commented on PDB-4174 Re: Encoding issue submitting facts from package inventory Erik Hansen we know what's going on now – the package inventory isn't currently subject to the null rewriting mentioned above. cf. PE-22576 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-4334) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.1)
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4334 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.1) Change By: Austin Blatt Resolution: Fixed Assignee: Eric Thompson Austin Blatt Status: Ready for Engineering Resolved 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-4339) massive failures connecting to puppetdb
Title: Message Title Austin Blatt commented on PDB-4339 Re: massive failures connecting to puppetdb That looks like Puppet Server's generic log message for a failure response from PuppetDB, can you find the error from your PuppetDB log as well? 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-4339) massive failures connecting to puppetdb
Title: Message Title luis created an issue PuppetDB / PDB-4339 massive failures connecting to puppetdb Issue Type: Bug Assignee: Unassigned Created: 2019/04/11 10:50 AM Priority: Major Reporter: luis I managed around 1000 nodes in our stg environment and I get daily reports like the one below from different servers. My puppet server got 20GB ram and 8 CPUs . It rans puppet server and puppetdb , Java memory for puppetserver is 12 Gb and 3 Gb for puppetdb, I have tried to tunning the settings, but I have not seen improvements 2019-04-11T02:52:52.616-07:00 ERROR [qtp974514354-53945] [puppetserver] Puppet Failed to execute '/pdb/cmd/v1?checksum=9be7293b34465f977f72a402b1def5b85a041266=9=HOSTNAME=replace_catalog=2019-04-11T09:52:11.981Z' on at least 1 of the following 'server_urls': https://PUPPETDBHOSTNAME:8081 2019 PuppetDB v6.3.0 Add Comment
Jira (BOLT-1242) run_as on localhost bugs
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1242 run_as on localhost bugs Issue Type: Bug Assignee: Lucy Wyman Created: 2019/04/11 10:46 AM Priority: Normal Reporter: Lucy Wyman This ticket captures 2 bugs: 1. When the user doesn't have a password (but can escalate without a password) we still try to look for the prompt even though one won't be printed. This ensure that if we try to read a prompt and there is no output to be read, we catch the error and return an empty string to node output. 2. When the user has stdin as an input method but does not read from stdin the input stream may close before we try to write to it. We should catch this error as well and mark the stdin stream as closed. Add Comment
Jira (PDB-4271) Create a new query endpoint/AST entity to query certname lifetime data
Title: Message Title Robert Roland updated an issue PuppetDB / PDB-4271 Create a new query endpoint/AST entity to query certname lifetime data Change By: Robert Roland Release Notes Summary: Experimental feature.The /nodes query endpoint will now return two additional fields indicating if the node has been configured to never expire its facts. To view these fields in a query, you must add the "include_fact_expiration=true" argument to your query string. Release Notes: New Feature 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-4275) Support import/export of "configure expiration" commands
Title: Message Title Robert Roland updated an issue PuppetDB / PDB-4275 Support import/export of "configure expiration" commands Change By: Robert Roland Release Notes Summary: This adds information about which nodes have fact expiration disabled to the import and export tarball from PuppetDB. Release Notes: New Feature 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-4315) Handle resource-event duplicates in reports
Title: Message Title Robert Roland updated an issue PuppetDB / PDB-4315 Handle resource-event duplicates in reports Change By: Robert Roland Release Notes Summary: In fixing PDB-4312, we exposed a bug in the puppet agent that would send duplicate events for a failing exec call. That would cause reports to fail to insert into puppetdb. This fix adds additional columns to the primary key calculation for events, and ignores duplicate rows at insert. Release Notes: Bug Fix 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-1195) Generate a PP plan from a simple plan
Title: Message Title Lucy Wyman assigned an issue to Unassigned Puppet Task Runner / BOLT-1195 Generate a PP plan from a simple plan Change By: Lucy Wyman Assignee: Lucy Wyman 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-9565) Not possible to set Mutliple Logging Destination with puppet agent anymore
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-9565 Not possible to set Mutliple Logging Destination with puppet agent anymore Change By: Jacob Helwig Release Notes Summary: When the ability to specify a logging destination in puppet.conf was added, the ability to specify multiple logging destinations through the command line using the --logdest option was broken. The ability to specify multiple logging destinations on the command line has been fixed. Release Notes: Bug Fix 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-9502) codesigning puppet executables on macOS 10.14
Title: Message Title Gheorghe Popescu commented on PUP-9502 Re: codesigning puppet executables on macOS 10.14 Marshall Taylor that seems a different issue, could you open a ticket for it and provide all the details? 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-9502) codesigning puppet executables on macOS 10.14
Title: Message Title Gheorghe Popescu commented on PUP-9502 Re: codesigning puppet executables on macOS 10.14 PR for handling users on OS X 10.14: https://github.com/puppetlabs/puppet/pull/7479 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-9331) Puppet Runs fail if leftovers in /var/spool/cron are present
Title: Message Title Alexandru Popa assigned an issue to Alexandru Popa Puppet / PUP-9331 Puppet Runs fail if leftovers in /var/spool/cron are present Change By: Alexandru Popa Assignee: Enis Inan Alexandru Popa 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-9640) Fix puppet user management on OS X 10.14
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-9640 Fix puppet user management on OS X 10.14 Change By: Gheorghe Popescu Assignee: Gheorghe Popescu 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-9640) Fix puppet user management on OS X 10.14
Title: Message Title Gheorghe Popescu created an issue Puppet / PUP-9640 Fix puppet user management on OS X 10.14 Issue Type: Sub-task Assignee: Unassigned Created: 2019/04/11 4:21 AM Priority: Normal Reporter: Gheorghe Popescu 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
