Jira (FACT-1892) pe-task's facter_task is failing with the promotion of puppet-agent 5.5.6.180.g8b5d99d
Title: Message Title
Enis Inan commented on FACT-1892
Re: pe-task's facter_task is failing with the promotion of puppet-agent 5.5.6.180.g8b5d99d
Redirecting STDOUT to STDERR messes up Puppet::Util::Execution
enis:facter enis.inan$ irb
2.4.2 :001 > require 'puppet'
=> true
2.4.2 :002 > x = Puppet::Util::Execution.execute("echo CALLED_EXECUTE")
=> "CALLED_EXECUTE\n"
2.4.2 :003 > $stdout = $stderr
=> #>
2.4.2 :004 > x = Puppet::Util::Execution.execute("echo CALLED_EXECUTE")
CALLED_EXECUTE
=> ""
2.4.2 :005 > x
=> ""
And
Jira (FACT-1892) pe-task's facter_task is failing with the promotion of puppet-agent 5.5.6.180.g8b5d99d
Title: Message Title
Enis Inan commented on FACT-1892
Re: pe-task's facter_task is failing with the promotion of puppet-agent 5.5.6.180.g8b5d99d
There's several things going on here. Here's my custom fact:
Facter.add('custom_fact') do
setcode do
require 'puppet'
Puppet::Util::Execution.execute('echo THIS_SHOULD_NOT_PRINT')
STDOUT.puts("STDOUT")
'custom_fact'
end
end
Invoking facter:
[root@v4wf528eg09c0we ~]# facter --custom-dir CUSTOM_FACTS/ --json --debug --query custom_fact 2>/dev/null
CALLING EXECUTE, SHOULD NOT PRINT
STDOUT
Jira (FACT-1892) pe-task's facter_task is failing with the promotion of puppet-agent 5.5.6.180.g8b5d99d
Title: Message Title Enis Inan commented on FACT-1892 Re: pe-task's facter_task is failing with the promotion of puppet-agent 5.5.6.180.g8b5d99d Made this a facter ticket because that's what is causing this issue, specifically https://github.com/puppetlabs/facter/pull/1751/commits/4a7ddb9d4ece7af89ecf9546507fe11216d1be5b#diff-cfd7b7fce6a29f4dc809ee437588d58dR335 (I think that commit inadvertently redirected stderr to stdout) 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 (FACT-1892) pe-task's facter_task is failing with the promotion of puppet-agent 5.5.6.180.g8b5d99d
Title: Message Title Enis Inan moved an issue Facter / FACT-1892 pe-task's facter_task is failing with the promotion of puppet-agent 5.5.6.180.g8b5d99d Change By: Enis Inan Key: PE FACT - 25380 1892 Project: Puppet Enterprise [Internal] Facter 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-4160) Upgrade jetty to fix cve-2017-7658
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4160 Upgrade jetty to fix cve-2017-7658 Change By: Rob Browning Summary: Fix upgrade Upgrade jetty to fix cve-2017-7658 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-916) Download task content from the master
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-916 Download task content from the master Change By: Michael Smith 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 (BOLT-903) Add configurable log rotation to bolt-server
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-903 Add configurable log rotation to bolt-server Change By: Michael Smith 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-916) Download task content from the master
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-916 Download task content from the master Change By: Michael Smith 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-9249) Backport sensitive DSL method PUP-8514
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9249 Backport sensitive DSL method PUP-8514 Change By: Josh Cooper Sprint: Coremunity 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-8514) Puppet should have a way of defining properties or parameters for types as sensitive
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8514 Puppet should have a way of defining properties or parameters for types as sensitive Change By: Josh Cooper Currently we have this lovely dance we need to go through if we need to define a parameter or property as sensitive. You can see examples of this in file.rb and exec.rb ([https://github.com/puppetlabs/puppet/commit/abd866a648a32d3895011d25af5d4b3d994669c8 ). ] ) As it currently works, we can only set a specific instance as sensitive. We should be able to say all instances of a particular property/parameter are sensitive when defining it. 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-9249) Backport sensitive DSL method PUP-8514
Title: Message Title Josh Cooper created an issue Puppet / PUP-9249 Backport sensitive DSL method PUP-8514 Issue Type: Bug Assignee: Unassigned Created: 2018/10/18 5:07 PM Fix Versions: PUP 5.5.8 Priority: Normal Reporter: Josh Cooper To use the sensitive DSL method introduced in PUP-8514, you need to be on Puppet 6 or later. This is a problem if you're a module author and want to support pre-6 agents. For example the puppet_agent module used to upgrade agents relies on the yumrepo resource type, but the yumrepo_core module cannot be run on pre-6 agents. This ticket is to backport the PUP-8514 to 5.5.x. Add Comment
Jira (PUP-9249) Backport sensitive DSL method PUP-8514
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9249 Backport sensitive DSL method PUP-8514 Change By: Josh Cooper Team: Coremunity 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-906) Boilerplate Python code
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-906 Boilerplate Python code Change By: Michael Smith Release Notes Summary: Bolt now includes a helper class for writing python tasks. See the docs for 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 (BOLT-906) Boilerplate Python code
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-906 Boilerplate Python code Change By: Michael Smith 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 (BOLT-906) Boilerplate Python code
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-906 Boilerplate Python code Change By: Michael Smith 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 (FACT-1870) Stdout in facts invalidates formatted output (yaml/json)
Title: Message Title Michelle Fredette commented on FACT-1870 Re: Stdout in facts invalidates formatted output (yaml/json) Branan Riley - should this have a 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 (PDB-4145) Check builds, promote to PE (PuppetDB 5.2.5)
Title: Message Title Zachary Kent assigned an issue to Austin Blatt PuppetDB / PDB-4145 Check builds, promote to PE (PuppetDB 5.2.5) Change By: Zachary Kent Assignee: Zachary Kent 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-4146) Update winston (PuppetDB 5.2.5)
Title: Message Title Zachary Kent assigned an issue to Austin Blatt PuppetDB / PDB-4146 Update winston (PuppetDB 5.2.5) Change By: Zachary Kent Assignee: Zachary Kent 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-4144) Bump versions, push directly, and tag (PuppetDB 5.2.5)
Title: Message Title Zachary Kent assigned an issue to Austin Blatt PuppetDB / PDB-4144 Bump versions, push directly, and tag (PuppetDB 5.2.5) Change By: Zachary Kent Assignee: Zachary Kent 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-4143) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.5)
Title: Message Title Zachary Kent assigned an issue to Austin Blatt PuppetDB / PDB-4143 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.5) Change By: Zachary Kent Assignee: Zachary Kent 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-4142) Merge-up, branch, and create pipelines (PuppetDB 5.2.5)
Title: Message Title Zachary Kent assigned an issue to Austin Blatt PuppetDB / PDB-4142 Merge-up, branch, and create pipelines (PuppetDB 5.2.5) Change By: Zachary Kent Assignee: Zachary Kent 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 (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-459 Reboot a target and wait for it to become available. Change By: Alex Dreyer A lot of deployment workflows require a reboot step where the target will be inaccessible. There should be an option in plans to support this. h2. Solutionthere are 3 pieces to this solutionh3.reboot taskpuppetlabs-reboot should be bundled with bolt. We should add non-ruby implementations of it.h3. wait_until_available functionA new function should be added to boltlib that can wait for a target to become available. For pcp targets it should use the orchestrator inventory endpoint. h4 h5 . questionswhat should it be called?should it retry by default or should that require opt-in?see https://github.com/puppetlabs/puppetlabs-reboot/pull/171 for prior art.h3. reboot planWe should add a plan to the reboot module that reboots targets catching errors and then waits for targets to become available again. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-459 Reboot a target and wait for it to become available. 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 (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-459
Reboot a target and wait for it to become available.
Change By:
Alex Dreyer
A lot of deployment workflows require a reboot step where the target will be inaccessible. There should be an option in plans to support this.h2. Solution Should there are 3 pieces to this solutionh3.reboot taskpuppetlabs-reboot should be a special plan bundled with bolt. We should add non-ruby implementations of it.h3. wait_until_available function specifically targeted at rebooting? Should there be a plan A new function should be added to boltlib that waits can wait for a target to become available leaving . For pcp targets it should use the reboot to some other step? orchestrator inventory endpoint. Should there h4. questionswhat should it be a flag to run_* to signify the action will make the target inaccessible called ? Step one is probably to spike on a plan should it retry by default or should that will run a command, expect the execution to fail with a disconnect and then poll until the target is available again. require opt-in? {noformat} plan reboot( $nodes, $command see https: / task / script_params, $timeout = 120 ) { $result = run_task github.com / command puppetlabs / script()$rebooting_targets = $result puppetlabs-reboot/pull/171 for prior art . map |$r| { [types of disconnect] h3 . contains? $r.kind }.map |$r|{ $r.target }$failed = range(0, $timeout).reduce($rebooting_targets) |$down, $_| { $available = run_task(is_available, $down, _catch_errors => true) if $avilable.ok{ break [] }$available.error_set().targets } unless $failed.empty { fail_plan({ kind => 'bolt/ reboot -failed' , plan msg => "Failed We should add a plan to the reboot ${failed}", details =>{ "failed_target" => $failed }}{noformat} module that reboots targets catching errors and then waits for targets to become available again.
Add Comment
Jira (PDB-4142) Merge-up, branch, and create pipelines (PuppetDB 5.2.5)
Title: Message Title James Shen updated an issue PuppetDB / PDB-4142 Merge-up, branch, and create pipelines (PuppetDB 5.2.5) Change By: James Shen Flagged: Impediment 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-4143) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.5)
Title: Message Title James Shen updated an issue PuppetDB / PDB-4143 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.5) Change By: James Shen Flagged: Impediment 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-9241) Verify Hiera access to locally-scoped variables
Title: Message Title Greg Larkin commented on PUP-9241 Re: Verify Hiera access to locally-scoped variables Thank you Claire Cadman and not sure yet Henrik Lindberg, but I have asked the customer to supply his sample code, and he said he will do that tomorrow. I'll attach it here as soon as I get it. 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-9248) add support for devices to puppet ssl
Title: Message Title Thomas Kishel updated an issue Puppet / PUP-9248 add support for devices to puppet ssl Change By: Thomas Kishel Issue Type: Improvement Bug 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-9248) add support for devices to puppet ssl
Title: Message Title Thomas Kishel created an issue Puppet / PUP-9248 add support for devices to puppet ssl Issue Type: Improvement Affects Versions: PUP 6.0.0 Assignee: Unassigned Created: 2018/10/18 3:20 PM Priority: Normal Reporter: Thomas Kishel After PUP-9156 ... An SSL error involving a device prompts the user to run the 'puppet ssl clean' command which cleans agent ssl files instead of the device ssl files, and prompts the user to run 'puppet agent' instead of 'puppet device'. Add Comment
Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8002 "Attempt to redefine entity" caused by using a resource collector Change By: Henrik Lindberg Fix Version/s: PUP 6.1.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 (BOLT-916) Download task content from the master
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-916 Download task content from the master Change By: Michael Smith Fix Version/s: PE 2019.0.1 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-916) Download task content from the master
Title: Message Title Michael Smith commented on BOLT-916 Re: Download task content from the master Acceptance test is covered by ORCH-2257. Some cleanup in bolt-server left after updating Orchestrator. 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-906) Boilerplate Python code
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-906 Boilerplate Python code Change By: Michael Smith Assignee: Michael Smith 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-783) Dynamic inventory
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-783 Dynamic inventory Change By: Alex Dreyer This is a place holder for stories around making the inventory more dynamic to support use cases where information about target instances and config is discovered, created or modified during a bolt execution.Stories* I want to create a target in one step of plan and then add it to an inventory group for later steps* I want to lookup credentials for a target in a secret service like vault and add update them on targets in inventory* I want to install a PE agent over ssh and then upgrade the target to use the pcp transport.* I want to lookup inventory from an external datastore when running commands and tasks outside a plan * I want to discover cloud resources and use them as inventory. 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
Jira (BOLT-905) [SPIKE] Investigate performance issues around concurrent connections over winrm
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-905 [SPIKE] Investigate performance issues around concurrent connections over winrm 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-9247) Puppet pidlock checks only look for PID if it is running, not process name
Title: Message Title Mike Smith created an issue Puppet / PUP-9247 Puppet pidlock checks only look for PID if it is running, not process name Issue Type: Bug Affects Versions: PUP 6.0.2 Assignee: Unassigned Created: 2018/10/18 1:07 PM Priority: Normal Reporter: Mike Smith Puppet Version: 6.0.2 (or any) Puppet Server Version: 2018.1 OS Name/Version: Windows (linux most likely as well) When puppet runs it created the pidlock file with the pid of puppet. If puppet stops/crashes while running the lock file remains. Puppet reads the file, checks for pid as integer, and sees if that pid is running (system.kill(0) to see if alive). If ANY PID responds, it locks, even if the PID is not a puppet PID. Desired Behavior: Puppet should check PID to see if it is running and its puppet, not just running. Actual Behavior: if any process has that pid, puppet locks. Steps to replicate (tested on windows 2016 with Puppet 6.0.2) 1 - start puppet run with 'puppet agent -t' 2 - while running stop the puppet/puppet-pxp agent services 3 - open pidloclk file, there should be a PID there 4 - change PID lock file contents to any other currently running PID 5 - start puppet / run 'puppet agent -t' Add Comment
Jira (PDB-4162) Test merge 6.0.x
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4162 Test merge 6.0.x Issue Type: Bug Assignee: Unassigned Created: 2018/10/18 11:44 AM Priority: Normal Reporter: gepetto-bot 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.
Jira (PUP-9244) suidmanager test fails on non-Windows when running as root
Title: Message Title Kris Bosland commented on PUP-9244 Re: suidmanager test fails on non-Windows when running as root Merged into 5.5.x at 33ae661. 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-8036) Use of server_urls can cause misleading agent errors
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8036 Use of server_urls can cause misleading agent errors Change By: Melissa Stone Sprint: Coremunity Hopper 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-9076) Puppet agent should not fall back to puppet:0 when servers in server_list are unreachable
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9076 Puppet agent should not fall back to puppet:0 when servers in server_list are unreachable Change By: Melissa Stone Sprint: Coremunity Hopper 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-6885) Remove warning about server_list and server conflicting
Title: Message Title Melissa Stone commented on PUP-6885 Re: Remove warning about server_list and server conflicting Josh Cooper will any of the recent http client work impact the scope of this ticket? 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-7405) Puppet 6.0.0 Removals
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7405 Puppet 6.0.0 Removals Change By: Josh Cooper Epic Status: To Do 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 (PDB-3928) Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3928 Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern Change By: Zachary Kent Fix Version/s: PDB 6.y Fix Version/s: PDB 6.0.1 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-3928) Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3928 Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern Change By: Zachary Kent Fix Version/s: PDB 5.2.5 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-3928) Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3928 Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern Change By: Zachary Kent Release Notes Summary: Add support for fact blacklist regexes. Omit facts whose namecompletely matches any of the expressions provided. Add a"facts-blacklist-type" database configuration option which defaults to"literal", producing the existing behavior, but can be set to "regex"to indicate that the facts-blacklist items are java patterns. 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
Jira (BOLT-931) Task implementation should be located relative to others in installdir
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-931 Task implementation should be located relative to others in installdir Change By: Michael Smith 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-903) Add configurable log rotation to bolt-server
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-903 Add configurable log rotation to bolt-server Change By: Michael Smith Fix Version/s: BOLT Next Fix Version/s: PE 2019.0.1 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-903) Add configurable log rotation to bolt-server
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-903 Add configurable log rotation to bolt-server Change By: Michael Smith 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 (PUP-9156) Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent
Title: Message Title Thomas Kishel commented on PUP-9156 Re: Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent Gah, branch named and PR filed using PUP-9156. Let me know if you would like me to undo any of that. 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-9156) Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent
Title: Message Title Josh Cooper commented on PUP-9156 Re: Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent Thomas Kishel Could you file a new ticket for that? 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-9156) Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent
Title: Message Title Thomas Kishel commented on PUP-9156 Re: Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent I have a PR that may address this, posting soon ... 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-9195) Unable to modify user account expiry date when forcelocal == true
Title: Message Title Jacob Helwig commented on PUP-9195 Re: Unable to modify user account expiry date when forcelocal == true Merged to 5.5.x in f3fdac2a30. 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-9156) Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent
Title: Message Title Josh Cooper commented on PUP-9156 Re: Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent As long as ssldir is set correctly, then the derived settings will be based on that new value: irb(main):002:0> require 'puppet' => true irb(main):003:0> Puppet.initialize_settings => [:debug, :info, :notice, :warning, :err, :alert, :emerg, :crit] irb(main):004:0> Puppet[:ssldir] => "/Users/josh/.puppetlabs/etc/puppet/ssl" irb(main):005:0> Puppet[:hostcert] => "/Users/josh/.puppetlabs/etc/puppet/ssl/certs/localhost.pem" irb(main):006:0> Puppet[:ssldir] = "/Users/josh/.puppetlabs/etc/puppet/device/foo/ssl" => "/Users/josh/.puppetlabs/etc/puppet/device/foo/ssl" irb(main):007:0> Puppet[:hostcert] => "/Users/josh/.puppetlabs/etc/puppet/device/foo/ssl/certs/localhost.pem"
Jira (PUP-9195) Unable to modify user account expiry date when forcelocal == true
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9195 Unable to modify user account expiry date when forcelocal == true Change By: Melissa Stone Release Notes Summary: When `forcelocal` is true and `expiry` is set, we now use `usermod` to manage a user rather than `lusermod`. `lusermod` does not support `-e`, and so would fail the puppet run. 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-9195) Unable to modify user account expiry date when forcelocal == true
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9195 Unable to modify user account expiry date when forcelocal == true Change By: Melissa Stone Fix Version/s: PUP 6.0.z Fix Version/s: PUP 5.5.z 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-9195) Unable to modify user account expiry date when forcelocal == true
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9195 Unable to modify user account expiry date when forcelocal == true Change By: Melissa Stone Fix Version/s: PUP 6.0.z Fix Version/s: PUP 5.5.z Fix Version/s: PUP 6.0.4 Fix Version/s: PUP 5.5.8 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.
Jira (BOLT-941) Publish apply_helpers to forge and document it's installation
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-941 Publish apply_helpers to forge and document it's installation Issue Type: Task Assignee: Unassigned Created: 2018/10/18 8:53 AM Priority: Normal Reporter: Alex Dreyer To use apply with pcp nodes apply_helpers needs to be installed. It should be published to forge and documentation updated for it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-940) apply_prep doesn't work with pcp nodes and released puppet_agent
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-940 apply_prep doesn't work with pcp nodes and released puppet_agent Change By: Alex Dreyer Summary: apply_prep doesn't work with pcp nodes . and released puppet_agent 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-940) apply_prep doesn't work with pcp nodes.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-940 apply_prep doesn't work with pcp nodes. Change By: Alex Dreyer Summary: apply prep should not try to install the agent on apply_prep doesn't work with pcp nodes . 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-940) apply prep should not try to install the agent on pcp nodes
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-940 apply prep should not try to install the agent on pcp nodes Issue Type: Bug Assignee: Unassigned Created: 2018/10/18 8:41 AM Priority: Normal Reporter: Alex Dreyer The puppet_agent tasks aren't released to forge yet and that makes it hard to use apply_prep with pcp nodes. Those nodes must have an agent on them already so we can skip agent installation and just collect facts for them. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9156) Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent
Title: Message Title Maggie Dreyer commented on PUP-9156 Re: Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent Okay, looking at the code for the clean command, I think I see what's wrong. It does not use the `ssldir` setting to find files to delete, but rather looks at the values of hostcert, hostprivkey, etc. directly. Are those configured separately to point to agent files, rather than inheriting from ssldir on device nodes? 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-269) Support documenting required modules
Title: Message Title DO! DevOps created an issue Puppet Strings / PDOC-269 Support documenting required modules Issue Type: New Feature Assignee: Unassigned Created: 2018/10/18 1:54 AM Priority: Normal Reporter: DO! DevOps It would be great if there was a tag to document forge modules that are used by the current class or type. I'd suggest a @uses-module: # @uses puppetlabs-stdlib This would render a link to the forge site of the puppetlabs-stdlib module. Add Comment
Jira (PUP-2175) Consider Adding Provider To The Default Output of `puppet resource package`
Title: Message Title Enis Inan assigned an issue to Enis Inan Puppet / PUP-2175 Consider Adding Provider To The Default Output of `puppet resource package` Change By: Enis Inan Assignee: Enis Inan 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.
