Jira (FACT-1884) Add NIM master detection
Title: Message Title Sebastian Miclea assigned an issue to Sebastian Miclea Facter / FACT-1884 Add NIM master detection Change By: Sebastian Miclea Assignee: Sebastian Miclea 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.276290.1537303892000.50876.1560840300243%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9720) puppet agent --fingerprint is broken
Title: Message Title Josh Cooper commented on PUP-9720 Re: puppet agent --fingerprint is broken Merged to 6.4.x in https://github.com/puppetlabs/puppet/commit/b0bc814212a0cbb271f245f7ddd700d1dd913da4 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310230.1558735767000.50775.1560819480118%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1403) Prepare bolt-server for bolt_shim removal
Title: Message Title Casey Williams commented on BOLT-1403 Re: Prepare bolt-server for bolt_shim removal Here's a first PR that addresses the JSON schema part: https://github.com/puppetlabs/bolt/pull/1042 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312897.1560810439000.50749.1560817500105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9644) Improve documentation around sensitive data in puppet
Title: Message Title Jean Bond assigned an issue to Jean Bond Puppet / PUP-9644 Improve documentation around sensitive data in puppet 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.304741.1555347266000.50696.1560815280178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1403) Prepare bolt-server for bolt_shim removal
Title: Message Title
Casey Williams updated an issue
Puppet Task Runner / BOLT-1403
Prepare bolt-server for bolt_shim removal
Change By:
Casey Williams
In support There are places in bolt-server where it is assumed that "task run" is the only type of spec testing for action that bolt server will run. Before we do BOLT-1400, BOLT-1401, and BOLT-1402, we want to look over the existing bolt-server code and find places where it makes sense to refactor things in an action-agnostic way, so that functionality can be reused for other bolt actions, like "command run", "upload file", and "run script". *In scope:* * *JSON schemas:* The bolt server app reuses a partial json schema for task details in both the ssh and winrm request schemas (see them [here|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server/schemas]). We will also want to reuse the target schemas for winrm and ssh while creating new endpoints for other actions. Refactor the task endpoint schemas so that they load details about target parameters from two new schemas, one each for winrm and ssh targets. * *Spec tests:* Look at the following tests and refactor where warranted so that they can more easily test other bolt actions besides "task run" ("command run", "file upload", "script run"). * * [https://github.com/puppetlabs/bolt/blob/master/spec/bolt_server/transport_app_spec.rb] * * [https://github.com/puppetlabs/bolt/blob/master/spec/bolt_server/app_integration_spec.rb] ** Review these files and the three BOLT tickets and then extract any helpers, shared examples, etc. that seem appropriate. *Out of scope:* * This ticket concerns only refactors that apply to all bolt actions – refactors that apply to only one or a few actions should be ticketed separately. The purpose of this ticket is only to unblock BOLT-1400, BOLT-1401, BOLT-1402 as a group.
Add Comment
Jira (PUP-9693) Hiera Lookup Fails when convert_to is used
Title: Message Title Jean Bond commented on PUP-9693 Re: Hiera Lookup Fails when convert_to is used Thanks Josh! I figured, but I like to confirm. On Mon, Jun 17, 2019 at 2:00 PM Josh Cooper (JIRA) < – Jean Bond Sr Technical Writer Puppet 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307503.1557191729000.50639.1560813060282%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1403) Prepare bolt-server for bolt_shim removal
Title: Message Title Casey Williams updated an issue Puppet Task Runner / BOLT-1403 Prepare bolt-server for bolt_shim removal Change By: Casey Williams Summary: Refactor Prepare bolt-server spec tests in preparation for bolt_shim removal 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312897.1560810439000.50621.1560812822456%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1403) Refactor bolt-server spec tests in preparation for bolt_shim removal
Title: Message Title Casey Williams assigned an issue to Casey Williams Puppet Task Runner / BOLT-1403 Refactor bolt-server spec tests in preparation for bolt_shim removal Change By: Casey Williams Assignee: Casey Williams 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312897.1560810439000.50484.1560810600250%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1403) Refactor bolt-server spec tests in preparation for bolt_shim removal
Title: Message Title
Casey Williams created an issue
Puppet Task Runner / BOLT-1403
Refactor bolt-server spec tests in preparation for bolt_shim removal
Issue Type:
Task
Assignee:
Unassigned
Created:
2019/06/17 3:27 PM
Priority:
Normal
Reporter:
Casey Williams
In support of spec testing for BOLT-1400, BOLT-1401, and BOLT-1402, we want to look over the following tests and refactor where warranted so that they can more easily test other bolt actions besides "task run" ("command run", "file upload", "script run").
https://github.com/puppetlabs/bolt/blob/master/spec/bolt_server/transport_app_spec.rb
https://github.com/puppetlabs/bolt/blob/master/spec/bolt_server/app_integration_spec.rb
Review these files and the three BOLT tickets and then extract any helpers, shared examples, etc. that seem appropriate.
Add Comment
Jira (BOLT-1342) Help text should only list options for that command
Title: Message Title Tom Beech updated an issue Puppet Task Runner / BOLT-1342 Help text should only list options for that command Change By: Tom Beech 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310059.1558709649000.50422.1560809821008%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9745) resource api 'Attempt to redefine entity' generation issue
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9745 resource api 'Attempt to redefine entity' generation issue Change By: Josh Cooper Team: Coremunity Server 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310856.1559291364000.50234.1560807660749%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9745) resource api 'Attempt to redefine entity' generation issue
Title: Message Title Josh Cooper commented on PUP-9745 Re: resource api 'Attempt to redefine entity' generation issue Pretty sure this is a dup of PUP-9602 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310856.1559291364000.50230.1560807660559%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9720) puppet agent --fingerprint is broken
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9720 puppet agent --fingerprint is broken Change By: Josh Cooper Release Notes Summary: If the agent doesn't have a client cert yet, then `puppet agent --fingerprint` will now print the SHA256 digest of the certificate request (CSR) like it used to do in Puppet < 6.4. Note this the digest of the DER encoded certificate or CSR. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310230.1558735767000.50215.1560807300287%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9720) puppet agent --fingerprint is broken
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-9720 puppet agent --fingerprint is broken Change By: Josh Cooper Assignee: Josh Cooper 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310230.1558735767000.50218.1560807300429%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9638) Add an option to verify the CA bundle download against a fingerprint
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-9638 Add an option to verify the CA bundle download against a fingerprint Change By: Josh Cooper Assignee: Josh Cooper 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.304299.1554918771000.50219.1560807300479%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9638) Add an option to verify the CA bundle download against a fingerprint
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9638 Add an option to verify the CA bundle download against a fingerprint Change By: Josh Cooper Sprint: Coremunity Hopper Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.304299.1554918771000.50217.1560807300382%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9638) Add an option to verify the CA bundle download against a fingerprint
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9638 Add an option to verify the CA bundle download against a fingerprint Change By: Josh Cooper Release Notes Summary: If the `ca_fingerprint` puppet setting is set, then newly provisioned agents will verify the CA certificate when it is initially downloaded. This provides a way to securely bootstrap new agents. The setting should be set to the SHA256 digest of the CA certificate, which can be calculated on the puppetserver using:$ openssl dgst -sha256 -r /etc/puppetlabs/puppet/ssl/certs/ca.pem | cut -f1 -d' '67aa4502b29c54f2b0984a322f06032103d75de29401d1b4416cb4f4f6dd8504 Release Notes: Enhancement Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit
Jira (PUP-9720) puppet agent --fingerprint is broken
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9720 puppet agent --fingerprint is broken Change By: Josh Cooper Release Notes Summary: If the agent doesn't have a client cert yet, then `puppet agent --fingerprint` will now print the SHA256 digest of the certificate request (CSR) like it used to do in Puppet < 6.4. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310230.1558735767000.50174.1560806340172%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1921) Facter java class incorrectly using "FACTERDIR" environment variable
Title: Message Title Jean Bond commented on FACT-1921 Re: Facter java class incorrectly using "FACTERDIR" environment variable Mihai Buzgau, the docs note doesn't tell me anything about what behavior users might have encountered or what this changes for them. Can you tell me what users need to know about this change, please? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307655.1557260973000.50160.1560806100342%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9717) Puppet 6 client exits on start when it cannot connect to puppetserver
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9717 Puppet 6 client exits on start when it cannot connect to puppetserver Change By: Josh Cooper Release Notes Summary: Restores the behavior present in < 6.4 whereby non-onetime puppet runs will wait and retry if an error is encountered while bootstrapping the SSL subsystem. The wait interval is controlled by the existing `waitforcert` setting. Onetime puppet runs (such as `puppet agent --test/--onetime`) will not retry, and instead exit when the first error occurs. 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. To view this discussion on the web visit https://gro
Jira (PUP-9717) Puppet 6 client exits on start when it cannot connect to puppetserver
Title: Message Title Kris Bosland commented on PUP-9717 Re: Puppet 6 client exits on start when it cannot connect to puppetserver Merged to 6.4.x at ebed29d. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309697.1558538932000.50142.1560805680392%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1402) Add 'run_script' endpoint to bolt-server
Title: Message Title
Casey Williams updated an issue
Puppet Task Runner / BOLT-1402
Add 'run_script' endpoint to bolt-server
Change By:
Casey Williams
*Background*When told to run a task on some nodes, a PE master typically contacts the nodes over the PCP protocol. It sends a formatted request over PCP to the pxp-agent service running on the nodes, directing them to run the task locally. But if the nodes don't have a pxp-agent service running, the PE master must contact them via SSH or WinRM instead. For these cases, the PE master runs a "pe-bolt-server" service, which is a sinatra application that waits for post requests to /ssh/run_task or /winrm/run_task, then runs the task via an instance of the bolt executor, just like bolt does when you run a task via the CLI. Basically, it's a thin REST API wrapper around normal bolt "task run" operations that the PE master can use when there's no PXP agent to talk to over PCP.In PE Kearney, "task run" is the only supported action over PCP, so it follows that the only endpoints in the bolt-server REST API are for "task run". For other typical bolt actions ("command run", "file upload", "script run"), PCP operations are handled by wrapping any non-task action in an ephemeral task in order to use the "task run" endpoints.PCP-869 and ORCH-2306 describe the process of enabling "run script" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "run script" when there is no PCP transport available.*Requirements*Changes will be made to the [bolt server app|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server]: * The app follows the [json schema specification|https://json-schema.org/specification.html]. Add a description of the JSON schema for data passed to the new endpoints [here|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server/schemas]. This schema should match the one defined for the "script run" action in PCP-869. * Add new POST endpoints in the transport sinatra app [here|https://github.com/puppetlabs/bolt/blob/master/lib/bolt_server/transport_app.rb] to support running a script via SSH and WinRM, using the new JSON schema. * Document the new endpoints in the [developer-docs|https://github.com/puppetlabs/bolt/blob/master/developer-docs/]. *Testing* * Write RSpec tests for the changes to bolt [here|https://github.com/puppetlabs/bolt/tree/master/spec/bolt_server]. * Acceptance/integration tests on the orchestrator side exist for this code [here|https://github.com/puppetlabs/orchestrator/blob/lovejoy/test/puppetlabs/orchestrator/integration/bolt_server.clj], but updating them is *out of scope* for this ticket. *Do* run a quick manual test that the API endpoints work as expected on a running PE master, but making changes orchestrator to make use of the endpoints should be done as part of an ORCH ticket.
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title
Casey Williams updated an issue
Puppet Task Runner / BOLT-1400
Add 'run_command' endpoint to bolt-server
Change By:
Casey Williams
*Background*When told to run a task on some nodes, a PE master typically contacts the nodes over the PCP protocol. It sends a formatted request over PCP to the pxp-agent service running on the nodes, directing them to run the task locally. But if the nodes don't have a pxp-agent service running, the PE master must contact them via SSH or WinRM instead. For these cases, the PE master runs a "pe-bolt-server" service, which is a sinatra application that waits for post requests to /ssh/run_task or /winrm/run_task, then runs the task via an instance of the bolt executor, just like bolt does when you run a task via the CLI. Basically, it's a thin REST API wrapper around normal bolt "task run" operations that the PE master can use when there's no PXP agent to talk to over PCP.In PE Kearney, "task run" is the only supported action over PCP, so it follows that the only endpoints in the bolt-server REST API are for "task run". For other typical bolt actions ("command run", "file upload", "script run"), PCP operations are handled by wrapping any non-task action in an ephemeral task in order to use the "task run" endpoints.PCP-867 and ORCH-2304 describe process of enabling "command run" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "command run" when there is no PCP transport available.*Requirements*Changes will be made to the [bolt server app|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server]: * The app follows the [json schema specification|https://json-schema.org/specification.html]. Add a description of the JSON schema for data passed to the new endpoints [here|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server/schemas]. This schema should match the one defined for the command action in PCP-867, that is:{code}{"type": "object","properties": {"command": {"type": "string"}}}{code} * Add new POST endpoints in the transport sinatra app [here|https://github.com/puppetlabs/bolt/blob/master/lib/bolt_server/transport_app.rb] to support running a command via SSH and WinRM, using the new JSON schema. * Document the new endpoints in the [developer-docs|https://github.com/puppetlabs/bolt/blob/master/developer-docs/]. *Testing* * Write RSpec tests for the changes to bolt [here|https://github.com/puppetlabs/bolt/tree/master/spec/bolt_server]. * Acceptance/integration tests on the orchestrator side exist for this code [here|https://github.com/puppetlabs/orchestrator/blob/lovejoy/test/puppetlabs/orchestrator/integration/bolt_server.clj], but updating them is *out of scope* for this ticket. *Do* run a quick manual test that the API endpoints work as expected on a running PE master, but making changes orchestrator to make use of the endpoints should be done as part of an ORCH ticket.
Jira (BOLT-1401) Add 'upload_file' endpoint to bolt-server
Title: Message Title
Casey Williams updated an issue
Puppet Task Runner / BOLT-1401
Add 'upload_file' endpoint to bolt-server
Change By:
Casey Williams
*Background*When told to run a task on some nodes, a PE master typically contacts the nodes over the PCP protocol. It sends a formatted request over PCP to the pxp-agent service running on the nodes, directing them to run the task locally. But if the nodes don't have a pxp-agent service running, the PE master must contact them via SSH or WinRM instead. For these cases, the PE master runs a "pe-bolt-server" service, which is a sinatra application that waits for post requests to /ssh/run_task or /winrm/run_task, then runs the task via an instance of the bolt executor, just like bolt does when you run a task via the CLI. Basically, it's a thin REST API wrapper around normal bolt "task run" operations that the PE master can use when there's no PXP agent to talk to over PCP.In PE Kearney, "task run" is the only supported action over PCP, so it follows that the only endpoints in the bolt-server REST API are for "task run". For other typical bolt actions ("command run", "file upload", "script run"), PCP operations are handled by wrapping any non-task action in an ephemeral task in order to use the "task run" endpoints.PCP-868 and ORCH-2305 describe process of enabling "upload file" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "upload file" when there is no PCP transport available.*Requirements*Changes will be made to the [bolt server app|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server]: * The app follows the [json schema specification|https://json-schema.org/specification.html]. Add a description of the JSON schema for data passed to the new endpoints [here|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server/schemas]. This schema should match the one defined for the "file upload" action in PCP-868. * Add new POST endpoints in the transport sinatra app [here|https://github.com/puppetlabs/bolt/blob/master/lib/bolt_server/transport_app.rb] to support uploading a file via SSH and WinRM, using the new JSON schema. * Document the new endpoints in the [developer-docs|https://github.com/puppetlabs/bolt/blob/master/developer-docs/]. *Testing* * Write RSpec tests for the changes to bolt [here|https://github.com/puppetlabs/bolt/tree/master/spec/bolt_server]. * Acceptance/integration tests on the orchestrator side exist for this code [here|https://github.com/puppetlabs/orchestrator/blob/lovejoy/test/puppetlabs/orchestrator/integration/bolt_server.clj], but updating them is *out of scope* for this ticket. *Do* run a quick manual test that the API endpoints work as expected on a running PE master, but making changes orchestrator to make use of the endpoints should be done as part of an ORCH ticket.
Jira (PUP-9693) Hiera Lookup Fails when convert_to is used
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9693 Hiera Lookup Fails when convert_to is used Change By: Josh Cooper Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307503.1557191729000.50133.1560805200392%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9749) puppet generate types should be run when the puppetserver is upgraded
Title: Message Title Trevor Vaughan commented on PUP-9749 Re: puppet generate types should be run when the puppetserver is upgraded Given the comment from Henrik Lindberg, it would seem that the safe thing to do would be to run it and give people the ability to opt-out. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312214.1560355314000.50124.1560805020216%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9698) Backport PUP-8967 to 5.5.x
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9698 Backport PUP-8967 to 5.5.x Change By: Josh Cooper Fix Version/s: PUP 5.5.z Fix Version/s: PUP 5.5.15 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308037.1557423516000.50097.1560804061252%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9698) Backport PUP-8967 to 5.5.x
Title: Message Title Josh Cooper commented on PUP-9698 Re: Backport PUP-8967 to 5.5.x Follow up commit merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/2064e7dc9eb8ed750919e6739fc1a47a421542ed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308037.1557423516000.50092.1560804061013%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1402) Add 'run_script' endpoint to bolt-server
Title: Message Title
Casey Williams updated an issue
Puppet Task Runner / BOLT-1402
Add 'run_script' endpoint to bolt-server
Change By:
Casey Williams
*Background*When told to run a task on some nodes, a PE master typically contacts the nodes over the PCP protocol. It sends a formatted request over PCP to the pxp-agent service running on the nodes, directing them to run the task locally. But if the nodes don't have a pxp-agent service running, the PE master must contact them via SSH or WinRM instead. For these cases, the PE master runs a "pe-bolt-server" service, which is a sinatra application that waits for post requests to /ssh/run_task or /winrm/run_task, then runs the task via an instance of the bolt executor, just like bolt does when you run a task via the CLI. Basically, it's a thin REST API wrapper around normal bolt "task run" operations that the PE master can use when there's no PXP agent to talk to over PCP.In PE Kearney, "task run" is the only supported action over PCP, so it follows that the only endpoints in the bolt-server REST API are for "task run". For other typical bolt actions ("command run", "file upload", "script run"), PCP operations are handled by wrapping any non-task action in an ephemeral task in order to use the "task run" endpoints.PCP-869 and ORCH-2306 describe the process of enabling "run script" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "run script" when there is no PCP transport available.*Requirements*Changes will be made to the [bolt server app|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server]: * The app follows the [json schema specification|https://json-schema.org/specification.html]. Add a description of the JSON schema for data passed to the new endpoints [here|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server/schemas]. This schema should match the one defined for the "script run" action in PCP-869. * Add new POST endpoints in the transport sinatra app [here|https://github.com/puppetlabs/bolt/blob/master/lib/bolt_server/transport_app.rb] to support running a script via SSH and WinRM, using the new JSON schema.*Testing* * Write RSpec tests for the changes to bolt [here|https://github.com/puppetlabs/bolt/tree/master/spec/bolt_server]. * Acceptance/integration tests are also maintained from on the orchestrator side : add new integration test(s) exist for the interaction of the orchestrator and bolt-server while running a script this code [here|https://github.com/puppetlabs/orchestrator/blob/lovejoy/test/puppetlabs/orchestrator/integration/bolt_server.clj] , but updating them is *out of scope* for this ticket . *Do* run a quick manual test that the API endpoints work as expected on a running PE master, but making changes orchestrator to make use of the endpoints should be done as part of an ORCH ticket.
Jira (BOLT-1401) Add 'upload_file' endpoint to bolt-server
Title: Message Title
Casey Williams updated an issue
Puppet Task Runner / BOLT-1401
Add 'upload_file' endpoint to bolt-server
Change By:
Casey Williams
*Background*When told to run a task on some nodes, a PE master typically contacts the nodes over the PCP protocol. It sends a formatted request over PCP to the pxp-agent service running on the nodes, directing them to run the task locally. But if the nodes don't have a pxp-agent service running, the PE master must contact them via SSH or WinRM instead. For these cases, the PE master runs a "pe-bolt-server" service, which is a sinatra application that waits for post requests to /ssh/run_task or /winrm/run_task, then runs the task via an instance of the bolt executor, just like bolt does when you run a task via the CLI. Basically, it's a thin REST API wrapper around normal bolt "task run" operations that the PE master can use when there's no PXP agent to talk to over PCP.In PE Kearney, "task run" is the only supported action over PCP, so it follows that the only endpoints in the bolt-server REST API are for "task run". For other typical bolt actions ("command run", "file upload", "script run"), PCP operations are handled by wrapping any non-task action in an ephemeral task in order to use the "task run" endpoints.PCP-868 and ORCH-2305 describe process of enabling "upload file" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "upload file" when there is no PCP transport available.*Requirements*Changes will be made to the [bolt server app|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server]: * The app follows the [json schema specification|https://json-schema.org/specification.html]. Add a description of the JSON schema for data passed to the new endpoints [here|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server/schemas]. This schema should match the one defined for the "file upload" action in PCP-868. * Add new POST endpoints in the transport sinatra app [here|https://github.com/puppetlabs/bolt/blob/master/lib/bolt_server/transport_app.rb] to support uploading a file via SSH and WinRM, using the new JSON schema.*Testing* * Write RSpec tests for the changes to bolt [here|https://github.com/puppetlabs/bolt/tree/master/spec/bolt_server]. * Acceptance/integration tests are also maintained from on the orchestrator side : add new integration test(s) exist for the interaction of the orchestrator and bolt-server while uploading a file this code [here|https://github.com/puppetlabs/orchestrator/blob/lovejoy/test/puppetlabs/orchestrator/integration/bolt_server.clj] , but updating them is *out of scope* for this ticket . *Do* run a quick manual test that the API endpoints work as expected on a running PE master, but making changes orchestrator to make use of the endpoints should be done as part of an ORCH ticket.
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title
Casey Williams updated an issue
Puppet Task Runner / BOLT-1400
Add 'run_command' endpoint to bolt-server
Change By:
Casey Williams
*Background*When told to run a task on some nodes, a PE master typically contacts the nodes over the PCP protocol. It sends a formatted request over PCP to the pxp-agent service running on the nodes, directing them to run the task locally. But if the nodes don't have a pxp-agent service running, the PE master must contact them via SSH or WinRM instead. For these cases, the PE master runs a "pe-bolt-server" service, which is a sinatra application that waits for post requests to /ssh/run_task or /winrm/run_task, then runs the task via an instance of the bolt executor, just like bolt does when you run a task via the CLI. Basically, it's a thin REST API wrapper around normal bolt "task run" operations that the PE master can use when there's no PXP agent to talk to over PCP.In PE Kearney, "task run" is the only supported action over PCP, so it follows that the only endpoints in the bolt-server REST API are for "task run". For other typical bolt actions ("command run", "file upload", "script run"), PCP operations are handled by wrapping any non-task action in an ephemeral task in order to use the "task run" endpoints.PCP-867 and ORCH-2304 describe process of enabling "command run" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "command run" when there is no PCP transport available.*Requirements*Changes will be made to the [bolt server app|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server]: * The app follows the [json schema specification|https://json-schema.org/specification.html]. Add a description of the JSON schema for data passed to the new endpoints [here|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server/schemas]. This schema should match the one defined for the command action in PCP-867, that is:{code}{"type": "object","properties": {"command": {"type": "string"}}}{code} * Add new POST endpoints in the transport sinatra app [here|https://github.com/puppetlabs/bolt/blob/master/lib/bolt_server/transport_app.rb] to support running a command via SSH and WinRM, using the new JSON schema.*Testing* * Write RSpec tests for the changes to bolt [here|https://github.com/puppetlabs/bolt/tree/master/spec/bolt_server]. * Acceptance/integration tests are also maintained from on the orchestrator side : add new integration test(s) exist for the interaction of the orchestrator and bolt-server while running a command this code [here|https://github.com/puppetlabs/orchestrator/blob/ 7a145bc93b33a1de075c95812ba39ed7eb198cc5 lovejoy /test/puppetlabs/orchestrator/integration/bolt_server.clj] , but updating them is *out of scope* for this ticket . *Do* run a quick manual test that the API endpoints work as expected on a running PE master, but making changes orchestrator to make use of the endpoints should be d
Jira (PUP-9693) Hiera Lookup Fails when convert_to is used
Title: Message Title Jean Bond commented on PUP-9693 Re: Hiera Lookup Fails when convert_to is used Josh Cooper, I assume this is going into 6.0.10 and 6.4.3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307503.1557191729000.50021.1560802320263%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title Sean McDonald updated an issue Puppet Task Runner / BOLT-1400 Add 'run_command' endpoint to bolt-server Change By: Sean McDonald Sprint: Skeletor Kanban 20190619 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.49994.1560801360656%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title Sean McDonald assigned an issue to Casey Williams Puppet Task Runner / BOLT-1400 Add 'run_command' endpoint to bolt-server Change By: Sean McDonald Assignee: Casey Williams 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.49996.1560801360750%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1401) Add 'upload_file' endpoint to bolt-server
Title: Message Title
Casey Williams updated an issue
Puppet Task Runner / BOLT-1401
Add 'upload_file' endpoint to bolt-server
Change By:
Casey Williams
*Background*When told to run a task on some nodes, a PE master typically contacts the nodes over the PCP protocol. It sends a formatted request over PCP to the pxp-agent service running on the nodes, directing them to run the task locally. But if the nodes don't have a pxp-agent service running, the PE master must contact them via SSH or WinRM instead. For these cases, the PE master runs a "pe-bolt-server" service, which is a sinatra application that waits for post requests to /ssh/run_task or /winrm/run_task, then runs the task via an instance of the bolt executor, just like bolt does when you run a task via the CLI. Basically, it's a thin REST API wrapper around normal bolt "task run" operations that the PE master can use when there's no PXP agent to talk to over PCP.In PE Kearney, "task run" is the only supported action over PCP, so it follows that the only endpoints in the bolt-server REST API are for "task run". For other typical bolt actions ("command run", "file upload", "script run"), PCP operations are handled by wrapping any non-task action in an ephemeral task in order to use the "task run" endpoints.PCP-868 and ORCH-2305 describe process of enabling "upload file" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "upload file" when there is no PCP transport available.*Requirements*Changes will be made to the [bolt server app|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server]: * The app follows the [json schema specification|https://json-schema.org/specification.html]. Add a description of the JSON schema for data passed to the new endpoints [here|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server/schemas]. This schema should match the one defined for the command "file upload" action in PCP-868. * Add new POST endpoints in the transport sinatra app [here|https://github.com/puppetlabs/bolt/blob/master/lib/bolt_server/transport_app.rb] to support uploading a file via SSH and WinRM, using the new JSON schema.*Testing* * Write RSpec tests for the changes to bolt [here|https://github.com/puppetlabs/bolt/tree/master/spec/bolt_server]. * Acceptance/integration tests are also maintained from the orchestrator side: add new integration test(s) for the interaction of the orchestrator and bolt-server while uploading a file [here|https://github.com/puppetlabs/orchestrator/blob/lovejoy/test/puppetlabs/orchestrator/integration/bolt_server.clj].
Jira (BOLT-1402) Add 'run_script' endpoint to bolt-server
Title: Message Title
Casey Williams created an issue
Puppet Task Runner / BOLT-1402
Add 'run_script' endpoint to bolt-server
Issue Type:
Task
Assignee:
Unassigned
Created:
2019/06/17 12:50 PM
Priority:
Normal
Reporter:
Casey Williams
Background When told to run a task on some nodes, a PE master typically contacts the nodes over the PCP protocol. It sends a formatted request over PCP to the pxp-agent service running on the nodes, directing them to run the task locally. But if the nodes don't have a pxp-agent service running, the PE master must contact them via SSH or WinRM instead. For these cases, the PE master runs a "pe-bolt-server" service, which is a sinatra application that waits for post requests to /ssh/run_task or /winrm/run_task, then runs the task via an instance of the bolt executor, just like bolt does when you run a task via the CLI. Basically, it's a thin REST API wrapper around normal bolt "task run" operations that the PE master can use when there's no PXP agent to talk to over PCP. In PE Kearney, "task run" is the only supported action over PCP, so it follows that the only endpoints in the bolt-server REST API are for "task run". For other typical bolt actions ("command run", "file upload", "script run"), PCP operations are handled by wrapping any non-task action in an ephemeral task in order to use the "task run" endpoints. PCP-869 and ORCH-2306 describe the process of enabling "run script" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "run script" when there is no PCP transport available. Requirements Changes will be made to the bolt server app:
The app follows the json schema specification. Add a description of the JSON schema for data passed to the new endpoints here. This schema should match the one defined for the "script run" action in PCP-869.
Add new POST endpoints in the trans
Jira (BOLT-1401) Add 'upload_file' endpoint to bolt-server
Title: Message Title
Casey Williams created an issue
Puppet Task Runner / BOLT-1401
Add 'upload_file' endpoint to bolt-server
Issue Type:
Task
Assignee:
Unassigned
Created:
2019/06/17 12:44 PM
Priority:
Normal
Reporter:
Casey Williams
Background When told to run a task on some nodes, a PE master typically contacts the nodes over the PCP protocol. It sends a formatted request over PCP to the pxp-agent service running on the nodes, directing them to run the task locally. But if the nodes don't have a pxp-agent service running, the PE master must contact them via SSH or WinRM instead. For these cases, the PE master runs a "pe-bolt-server" service, which is a sinatra application that waits for post requests to /ssh/run_task or /winrm/run_task, then runs the task via an instance of the bolt executor, just like bolt does when you run a task via the CLI. Basically, it's a thin REST API wrapper around normal bolt "task run" operations that the PE master can use when there's no PXP agent to talk to over PCP. In PE Kearney, "task run" is the only supported action over PCP, so it follows that the only endpoints in the bolt-server REST API are for "task run". For other typical bolt actions ("command run", "file upload", "script run"), PCP operations are handled by wrapping any non-task action in an ephemeral task in order to use the "task run" endpoints. PCP-868 and ORCH-2305 describe process of enabling "upload file" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "upload file" when there is no PCP transport available. Requirements Changes will be made to the bolt server app:
The app follows the json schema specification. Add a description of the JSON schema for data passed to the new endpoints here. This schema should match the one defined for the command action in PCP-868.
Add new POST endpoints in the transport s
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title
Casey Williams updated an issue
Puppet Task Runner / BOLT-1400
Add 'run_command' endpoint to bolt-server
Change By:
Casey Williams
*Background*When told to run a task on some nodes, a PE master typically contacts the nodes over the PCP protocol. It sends a formatted request over PCP to the pxp-agent service running on the nodes, directing them to run the task locally. But if the nodes don't have a pxp-agent service running, the PE master must contact them via SSH or WinRM instead. For these cases, the PE master runs a "pe-bolt-server" service, which is a sinatra application that waits for post requests to /ssh/run_task or /winrm/run_task, then runs the task via an instance of the bolt executor, just like bolt does when you run a task via the CLI. Basically, it's a thin REST API wrapper around normal bolt "task run" operations that the PE master can use when there's no PXP agent to talk to over PCP.In PE Kearney, "task run" is the only supported action over PCP, so it follows that the only endpoints in the bolt-server REST API are for "task run". For other typical bolt actions ("command run", "file upload", "script run"), PCP operations are handled by wrapping any non-task action in an ephemeral task in order to use the "task run" endpoints.PCP-867 and ORCH-2304 describe process of enabling "command run" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "command run" when there is no PCP transport available.*Requirements*Changes will be made to the [bolt server app|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server]: * The app follows the [json schema specification|https://json-schema.org/specification.html]. Add a description of the JSON schema for data passed to the new endpoints [here|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server/schemas]. This schema should match the one defined for the command action in PCP-867, that is:{code}{"type": "object","properties": {"command": {"type": "string"}}}{code} * Add new POST endpoints in the transport sinatra app [here|https://github.com/puppetlabs/bolt/blob/master/lib/bolt_server/transport_app.rb] to support running a command via SSH and WinRM, using the new JSON schema.*Testing* * Write RSpec tests for the changes to bolt [here|https://github.com/puppetlabs/bolt/tree/master/spec/bolt_server]. * Acceptance/integration tests are also maintained from the orchestrator side: add new integration test(s) for the interaction of the orchestrator and bolt-server while running a command [here|https://github.com/puppetlabs/orchestrator/blob/7a145bc93b33a1de075c95812ba39ed7eb198cc5/test/puppetlabs/orchestrator/integration/bolt_server.clj].
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title Casey Williams updated an issue Puppet Task Runner / BOLT-1400 Add 'run_command' endpoint to bolt-server Change By: Casey Williams Story Points: 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.49963.1560800460178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title Casey Williams updated an issue Puppet Task Runner / BOLT-1400 Add 'run_command' endpoint to bolt-server Change By: Casey Williams Team: Skeletor 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.49962.1560800460124%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title
Casey Williams created an issue
Puppet Task Runner / BOLT-1400
Add 'run_command' endpoint to bolt-server
Issue Type:
Task
Assignee:
Unassigned
Created:
2019/06/17 12:38 PM
Priority:
Normal
Reporter:
Casey Williams
Background When told to run a task on some nodes, a PE master typically contacts the nodes over the PCP protocol. It sends a formatted request over PCP to the pxp-agent service running on the nodes, directing them to run the task locally. But if the nodes don't have a pxp-agent service running, the PE master must contact them via SSH or WinRM instead. For these cases, the PE master runs a "pe-bolt-server" service, which is a sinatra application that waits for post requests to /ssh/run_task or /winrm/run_task, then runs the task via an instance of the bolt executor, just like bolt does when you run a task via the CLI. Basically, it's a thin REST API wrapper around normal bolt "task run" operations that the PE master can use when there's no PXP agent to talk to over PCP. In PE Kearney, "task run" is the only supported action over PCP, so it follows that the only endpoints in the bolt-server REST API are for "task run". For other typical bolt actions ("command run", "file upload", "script run"), PCP operations are handled by wrapping any non-task action in an ephemeral task in order to use the "task run" endpoints. PCP-867 and ORCH-2304 describe process of enabling "command run" over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "command run" when there is no PCP transport available. Requirements Changes will be made to the bolt server app:
The app follows the json schema specification. Add a description of the JSON schema for data passed to the new endpoints here. This schema should match the one defined for the command action in PCP-867, that is:
Jira (PUP-9566) Allow to send extra headers when requesting a catalog compilation
Title: Message Title Ethan Brown commented on PUP-9566 Re: Allow to send extra headers when requesting a catalog compilation Thanks for the comments Josh Cooper What other HTTP requests does Puppet make outside of requests to Puppetserver and HTTP backed file resources? Would hostname matching be a good mechanism for restricting headers for specific use cases? I'm thinking about something like csr_attributes - i.e. a separate YAML map of host -> array of additional headers. That's probably more complexity than we would want to add for this and it may become difficult to keep the server hostname in puppet.conf synchronized with a new sidecar file (rather than just using the servers hostname automatically to restrict) - but trying to come up with something that isn't so hardcoded around the identity of puppetserver. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300606.1552923936000.49951.1560799860846%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4418) Update winston (PuppetDB 6.3.4)
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4418 Update winston (PuppetDB 6.3.4) Change By: Zachary Kent Fix Version/s: pdb 6.3.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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312795.1560728318000.49734.1560794281272%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4417) Check builds, promote to PE (PuppetDB 6.3.4)
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4417 Check builds, promote to PE (PuppetDB 6.3.4) Change By: Zachary Kent Fix Version/s: pdb 6.3.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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312793.1560728302000.49731.1560794281125%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4416) Bump versions, push directly, and tag (PuppetDB 6.3.4)
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4416 Bump versions, push directly, and tag (PuppetDB 6.3.4) Change By: Zachary Kent Fix Version/s: pdb 6.3.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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312792.1560728296000.49726.1560794280887%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4415) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.4)
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4415 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.4) Change By: Zachary Kent Fix Version/s: pdb 6.3.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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312791.1560728289000.49713.1560794220954%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4414) Merge-up, branch, and create pipelines (PuppetDB 6.3.4)
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4414 Merge-up, branch, and create pipelines (PuppetDB 6.3.4) Change By: Zachary Kent Fix Version/s: pdb 6.3.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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312790.1560728283000.49721.1560794221340%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9748) Puppet Device doesn't honor ENC-set Environment in 5.5.10 or later
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9748 Puppet Device doesn't honor ENC-set Environment in 5.5.10 or later Change By: Jorie Tappa Team: Network Automation 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312177.1560307583000.49513.1560790440201%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4418) Update winston (PuppetDB 6.3.4)
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4418 Update winston (PuppetDB 6.3.4) Change By: Zachary Kent Summary: Update winston (PuppetDB 6.3. 3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312795.1560728318000.49508.1560790320390%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4417) Check builds, promote to PE (PuppetDB 6.3.4)
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4417 Check builds, promote to PE (PuppetDB 6.3.4) Change By: Zachary Kent Summary: Check builds, promote to PE (PuppetDB 6.3. 3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312793.1560728302000.49504.1560790261504%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4416) Bump versions, push directly, and tag (PuppetDB 6.3.4)
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4416 Bump versions, push directly, and tag (PuppetDB 6.3.4) Change By: Zachary Kent Summary: Bump versions, push directly, and tag (PuppetDB 6.3. 3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312792.1560728296000.49500.1560790261381%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4415) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.4)
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4415 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.4) Change By: Zachary Kent Summary: Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3. 3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312791.1560728289000.49496.1560790260963%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4414) Merge-up, branch, and create pipelines (PuppetDB 6.3.4)
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4414 Merge-up, branch, and create pipelines (PuppetDB 6.3.4) Change By: Zachary Kent Summary: Merge-up, branch, and create pipelines (PuppetDB 6.3. 3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312790.1560728283000.49492.1560790260767%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9750) optionally add pe_version to server_facts
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9750 optionally add pe_version to server_facts Change By: Jorie Tappa 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312257.156036703.49487.1560790201439%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4414) Merge-up, branch, and create pipelines (PuppetDB 6.3.3)
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4414 Merge-up, branch, and create pipelines (PuppetDB 6.3.3) Change By: Zachary Kent Comment: duplicates PDB-4392 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312790.1560728283000.49480.1560790201117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9753) XOR operator in Puppet Language
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9753 XOR operator in Puppet Language Change By: Jorie Tappa Team: Server 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312414.1560503163000.49461.1560790020320%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1361) Docs for plan parameters are confusing
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1361 Docs for plan parameters are confusing Change By: Lucy Wyman Labels: 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 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311199.155966702.49358.1560786780467%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1360) Evaluate including upgrades for bolt gem dependencies in bolt packages
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1360 Evaluate including upgrades for bolt gem dependencies in bolt packages 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311108.1559598816000.49253.1560784140069%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1399) Task action stub "parameter" method incorrectly merges options and arguments
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1399 Task action stub "parameter" method incorrectly merges options and arguments Issue Type: Bug Assignee: Unassigned Created: 2019/06/17 8:04 AM Priority: Normal Reporter: Cas Donoghue When and expectation fails and the parameters method is called to display the options and arguments an exception is raised when attempting to merge hashes with a `+` operator. https://github.com/puppetlabs/bolt/blob/de5fbd26dcf0be04e8e6c31e71f4201bb8027cf8/lib/bolt_spec/plans/action_stubs/task_stub.rb#L33 https://github.com/puppetlabs/bolt/blob/de5fbd26dcf0be04e8e6c31e71f4201bb8027cf8/lib/bolt_spec/plans/action_stubs.rb#L58 Add Comment
Jira (PUP-9744) Create acceptance test for PUP-9047
Title: Message Title David Schmitt commented on PUP-9744 Re: Create acceptance test for PUP-9047 David Mallon since I don't know who else (w|c|sh)ould be picking it up, I assigned it to our team. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311833.1560175214000.49139.1560771060223%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9753) XOR operator in Puppet Language
Title: Message Title Henrik Lindberg commented on PUP-9753 Re: XOR operator in Puppet Language IMO, XOR would be easier to understand for those that understand what XOR is, for others it is just trading one difficulty for another. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312414.1560503163000.49134.1560770700224%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9753) XOR operator in Puppet Language
Title: Message Title PU commented on PUP-9753 Re: XOR operator in Puppet Language Thank you for this alternative solution and the explanations. At the moment I agree that with this alternative an XOR operator isn't really needed although it would be better understandable. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312414.1560503163000.49125.1560770160156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9744) Create acceptance test for PUP-9047
Title: Message Title David Mallon commented on PUP-9744 Re: Create acceptance test for PUP-9047 David Schmitt is this something we will be picking 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311833.1560175214000.49104.1560768120250%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4401) puppetdb : Error while attempting to create connection pool
Title: Message Title zoen commented on PDB-4401 Re: puppetdb : Error while attempting to create connection pool the issue seems solved itself. I still do not understand what's happened. looking on logs: it seems that the refresh of Service[puppetdb] took more than 4 hours. the next run of puppet, it pushes Database_grant and puppetdb was happy with that. Someone can help me to understand.? thanks Jun 14 15:21:12 02 puppet-agent[1256]: (/Stage[main]/Puppetdb::Server/Ini_subsetting['-Xmx']/value) value changed '192m' to '2g' Jun 14 15:21:12 02 puppet-agent[1256]: (/Stage[main]/Puppetdb::Server/Ini_subsetting['-Xmx']) Scheduling refresh of Service[puppetdb] Jun 14 15:21:12 02 puppet-agent[1256]: (/Stage[main]/Puppetdb::Server/Ini_subsetting['-Xms']/ensure) created Jun 14 15:21:12 02 puppet-agent[1256]: (/Stage[main]/Puppetdb::Server/Ini_subsetting['-Xms']) Scheduling refresh of Service[puppetdb] Jun 14 15:27:40 02 puppet-agent[19742]: Run of Puppet configuration client already in progress; skipping (/opt/puppetlabs/puppet/cache/state/agent_catalog_run.lock exists) Jun 14 15:27:45 02 puppet-agent[19767]: Run of Puppet configuration client already in progress; skipping (/opt/puppetlabs/puppet/cache/state/agent_catalog_run.lock exists) Jun 14 15:31:41 02 puppet-agent[20306]: Run of Puppet configuration client already in progress; skipping (/opt/puppetlabs/puppet/cache/state/agent_catalog_run.lock exists) Jun 14 15:51:41 02 puppet-agent[22909]: Run of Puppet configuration client already in progress; skipping (/opt/puppetlabs/puppet/cache/state/agent_catalog_run.lock exists) Jun 14 16:11:41 02 puppet-agent[25523]:
Jira (PDB-4401) puppetdb : Error while attempting to create connection pool
Title: Message Title zoen updated an issue PuppetDB / PDB-4401 puppetdb : Error while attempting to create connection pool Change By: zoen Priority: Blocker Major 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312301.1560420511000.49055.1560762600757%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
