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 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.312897.1560810439000.8084.1562626560357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1339) Build pe-bolt-server for redhatfips-7-x86_64
Title: Message Title Casey Williams updated an issue Puppet Task Runner / BOLT-1339 Build pe-bolt-server for redhatfips-7-x86_64 Change By: Casey Williams Sprint: Skeletor Kanban 20190703 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.309966.155865044.2427.1562016360203%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1339) Build pe-bolt-server for redhatfips-7-x86_64
Title: Message Title Casey Williams commented on BOLT-1339 Re: Build pe-bolt-server for redhatfips-7-x86_64 This work should be done in https://github.com/puppetlabs/pe-bolt-vanagon 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.309966.155865044.2372.1562014800171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1339) Build pe-bolt-server for redhatfips-7-x86_64
Title: Message Title Casey Williams updated an issue Puppet Task Runner / BOLT-1339 Build pe-bolt-server for redhatfips-7-x86_64 Change By: Casey Williams Comment: There is a PR up for this here: https://github.com/puppetlabs/bolt-vanagon/pull/107 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.309966.155865044.2370.1562014800159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1339) Build pe-bolt-server for redhatfips-7-x86_64
Title: Message Title Casey Williams commented on BOLT-1339 Re: Build pe-bolt-server for redhatfips-7-x86_64 There is a PR up for this here: https://github.com/puppetlabs/bolt-vanagon/pull/107 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.309966.155865044.2368.1562014680088%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1339) Build pe-bolt-server for redhatfips-7-x86_64
Title: Message Title Casey Williams commented on BOLT-1339 Re: Build pe-bolt-server for redhatfips-7-x86_64 Once this work is ready in the pe-bolt-vanagon repo, we can revert this PR to enable it in CI: https://github.com/puppetlabs/ci-job-configs/pull/6047 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.309966.155865044.2366.1562014560327%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1339) Build pe-bolt-server for redhatfips-7-x86_64
Title: Message Title Casey Williams updated an issue Puppet Task Runner / BOLT-1339 Build pe-bolt-server for redhatfips-7-x86_64 Change By: Casey Williams Team: Bolt 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.309966.155865044.2357.1562014500285%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1339) Build pe-bolt-server for redhatfips-7-x86_64
Title: Message Title Casey Williams commented on BOLT-1339 Re: Build pe-bolt-server for redhatfips-7-x86_64 My team can take this over, I'll reassign 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.309966.155865044.2354.1562014500272%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 The final PR for this ticket is up, here: https://github.com/puppetlabs/bolt/pull/1059 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.1357.156176485%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 https://github.com/puppetlabs/bolt/pull/1053 is up to address the second bullet point here. Once that's merged, Jonathan Morris let's sync up on the spec test part. 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.58498.1561405200159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1847) Implement "cloud" fact Azure identification for Windows platform
Title: Message Title Casey Williams assigned an issue to Unassigned Facter / FACT-1847 Implement "cloud" fact Azure identification for Windows platform 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.247441.1524674206000.58448.1561404481430%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1779) Windows 2016 container not detected as virtual=docker by facter
Title: Message Title Casey Williams assigned an issue to Unassigned Facter / FACT-1779 Windows 2016 container not detected as virtual=docker by facter 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.216080.1507889554000.58455.1561404481770%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
There are places in bolt-server where it is assumed that "task run" is the only type of 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. * * SSH and WinRM route reuse:* There will be endpoints for each bolt action nested under the 'ssh' and 'winrm' route segments (/ssh/run_task, /ssh/run_command, /ssh/upload_file, etc.). There are a few cases (which are detailed in the transport app's spec tests) where a certain combination of parameters to an SSH or WinRM execution should be rejected and the request halted early – right now, this is done in the run_task handler, but we should break out the SSH and WinRM validations into their own functions and apply them using Sinatra's dynamic route handling, if possible. * * 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.
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 (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 (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-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 (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
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
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
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 (BOLT-1379) Document that "upload file" is able to handle directories as well as files
Title: Message Title Casey Williams updated an issue Puppet Task Runner / BOLT-1379 Document that "upload file" is able to handle directories as well as files Change By: Casey Williams 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.311900.1560188799000.40214.156010316%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1379) Document that "upload file" is able to handle directories as well as files
Title: Message Title Casey Williams updated an issue Puppet Task Runner / BOLT-1379 Document that "upload file" is able to handle directories as well as files 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.311900.1560188799000.40213.156010266%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1379) Document that "upload file" is able to handle directories as well as files
Title: Message Title Casey Williams created an issue Puppet Task Runner / BOLT-1379 Document that "upload file" is able to handle directories as well as files Issue Type: Task Assignee: Unassigned Created: 2019/06/10 10:46 AM Labels: docs Priority: Normal Reporter: Casey Williams The "upload file" function and command are able to handle directories as well as plain files, but the docs make no mention of directories – they should do so. Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-1379) Document that "upload file" is able to handle directories as well as files
Title: Message Title Casey Williams assigned an issue to Casey Williams Puppet Task Runner / BOLT-1379 Document that "upload file" is able to handle directories as well as files 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.311900.1560188799000.40211.1560188820378%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1914) Expose Facter.reset under jruby
Title: Message Title Casey Williams updated an issue Facter / FACT-1914 Expose Facter.reset under jruby Change By: Casey Williams Fix Version/s: FACT 3.13.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 (FACT-1914) Expose Facter.reset under jruby
Title: Message Title Casey Williams updated an issue Facter / FACT-1914 Expose Facter.reset under jruby Change By: Casey Williams Fix Version/s: FACT 3.13.1 Fix Version/s: FACT 3.13.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 (FACT-1914) Expose Facter.reset under jruby
Title: Message Title Casey Williams assigned an issue to Branan Riley Facter / FACT-1914 Expose Facter.reset under jruby Change By: Casey Williams Assignee: Branan Riley 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-1914) Expose Facter.reset under jruby
Title: Message Title Casey Williams created an issue Facter / FACT-1914 Expose Facter.reset under jruby Issue Type: Task Assignee: Unassigned Created: 2019/04/04 3:33 PM Priority: Normal Reporter: Casey Williams PAL calls Facter.reset here, but Facter.reset is not available under jruby. PAL will not be useful in orchestrator until facter.jar exposes reset. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1911) Cannot find libfacter when starting Server on RHEL 8
Title: Message Title Casey Williams moved an issue Facter / FACT-1911 Cannot find libfacter when starting Server on RHEL 8 Change By: Casey Williams Method Found: Needs Assessment Issue Type: Improvement Bug Key: SERVER FACT - 2496 1911 Project: Puppet Server 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
Jira (PUP-9336) Ensure provider suitability is always lazily evaluated
Title: Message Title Casey Williams commented on PUP-9336 Re: Ensure provider suitability is always lazily evaluated This work was reverted after merging up to the 6.0.x branch to allow the 6.2.0 release to proceed. I'll open a PR to un-revert it after the release is finished. 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-9336) Ensure provider suitability is always lazily evaluated
Title: Message Title Casey Williams updated an issue Puppet / PUP-9336 Ensure provider suitability is always lazily evaluated Change By: Casey Williams Fix Version/s: PUP 6.2.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 (PUP-9392) Text Fragmentation: Incomplete phrases in string resources
Title: Message Title Casey Williams commented on PUP-9392 Re: Text Fragmentation: Incomplete phrases in string resources Hi Erwin Hom, this will be released in puppet 6.2.0 – please add release notes if needed (or mark 'not needed') – thanks! 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-9392) Text Fragmentation: Incomplete phrases in string resources
Title: Message Title Casey Williams updated an issue Puppet / PUP-9392 Text Fragmentation: Incomplete phrases in string resources Change By: Casey Williams Fix Version/s: PUP 6.2.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 (PUP-5575) puppet.conf permission issues should be blocking - now silently ignoring error
Title: Message Title Casey Williams updated an issue Puppet / PUP-5575 puppet.conf permission issues should be blocking - now silently ignoring error Change By: Casey Williams Fix Version/s: PUP 6.2.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 (PUP-5287) install_options capability on Solaris provider "sun" & "pkg" - clone
Title: Message Title Casey Williams updated an issue Puppet / PUP-5287 install_options capability on Solaris provider "sun" & "pkg" - clone Change By: Casey Williams Fix Version/s: PUP 6.2.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 (PUP-9303) A heredoc with interpolation containing [ ] in the expression can cause syntax error
Title: Message Title Casey Williams updated an issue Puppet / PUP-9303 A heredoc with interpolation containing [ ] in the _expression_ can cause syntax error Change By: Casey Williams Fix Version/s: PUP 5.5.11 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-1906) networking.dhcp fact is blank on RedHat 8 beta
Title: Message Title
Casey Williams updated an issue
Facter / FACT-1906
networking.dhcp fact is blank on RedHat 8 beta
Change By:
Casey Williams
Tests for the dhcp fact on redhat 8 fail when enabled in the puppet-agent 5.5.x test suite. We've skipped this test in CI for now (see FACT-1905) , but we'd like this to to work correctly when the information is available.FWIW, It looks like the redhat 8 pooler machines _do_ have dhclient installed, but also have systemd-networkd in the mix . I would like us ; perhaps there is a new way to figure find this out information . {code:java}12:22:18 * Ensure the Networking fact resolves with reasonable values for at least one interface12:22:18 12:22:18 fzt7cberv6iwtxt.delivery.puppetlabs.net (fzt7cberv6iwtxt.delivery.puppetlabs.net) 20:22:18$ facter --json "networking.dhcp"12:22:18 {12:22:18 "networking.dhcp": ""12:22:18 }12:22:18 12:22:18 fzt7cberv6iwtxt.delivery.puppetlabs.net (fzt7cberv6iwtxt.delivery.puppetlabs.net) executed in 0.18 seconds12:22:18 Minitest::Assertion: Expected /^(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)$/ to match "". {code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1906) networking.dhcp fact is blank on RedHat 8 beta
Title: Message Title Casey Williams updated an issue Facter / FACT-1906 networking.dhcp fact is blank on RedHat 8 beta Change By: Casey Williams Labels: dhcp linux redhat 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-1906) networking.dhcp fact is blank on RedHat 8 beta
Title: Message Title
Casey Williams created an issue
Facter / FACT-1906
networking.dhcp fact is blank on RedHat 8 beta
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/01/17 10:32 AM
Priority:
Normal
Reporter:
Casey Williams
Tests for the dhcp fact on redhat 8 fail when enabled in the puppet-agent 5.5.x test suite. We've skipped this test in CI for now, but we'd like to to work correctly when the information is available. FWIW, It looks like the redhat 8 pooler machines do have dhclient installed, but also have systemd-networkd in the mix. I would like us to figure this out.
12:22:18 * Ensure the Networking fact resolves with reasonable values for at least one interface12:22:18 12:22:18 fzt7cberv6iwtxt.delivery.puppetlabs.net (fzt7cberv6iwtxt.delivery.puppetlabs.net) 20:22:18$ facter --json "networking.dhcp"12:22:18 {12:22:18 "networking.dhcp": ""12:22:18 }12:22:18 12:22:18 fzt7cberv6iwtxt.delivery.puppetlabs.net (fzt7cberv6iwtxt.delivery.puppetlabs.net) executed in 0.18 seconds12:22:18 Minitest::Assertion: Expected /^(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)$/ to match "".
Jira (FACT-1905) Facter networking fact tests fail on redhat 8
Title: Message Title Casey Williams updated an issue Facter / FACT-1905 Facter networking fact tests fail on redhat 8 Change By: Casey Williams Team: Puppet Romania 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-1905) Facter networking fact tests fail on redhat 8
Title: Message Title Casey Williams moved an issue Facter / FACT-1905 Facter networking fact tests fail on redhat 8 Change By: Casey Williams Key: PA FACT - 2399 1905 Project: Puppet Agent 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 (PUP-5287) install_options capability on Solaris provider "sun" & "pkg" - clone
Title: Message Title Casey Williams commented on PUP-5287 Re: install_options capability on Solaris provider "sun" & "pkg" - clone This PR is up for pkg – it looks like install_options was already implemented for sun at some point. 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-9313) String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows
Title: Message Title Casey Williams updated an issue Puppet / PUP-9313 String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows Change By: Casey Williams Labels: yaml 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-9313) String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows
Title: Message Title Casey Williams updated an issue Puppet / PUP-9313 String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows Change By: Casey Williams Labels: ruby yaml 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-9313) String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows
Title: Message Title Casey Williams updated an issue Puppet / PUP-9313 String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows Change By: Casey Williams Sprint: Platform OS 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-9313) String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows
Title: Message Title Casey Williams assigned an issue to Casey Williams Puppet / PUP-9313 String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5287) install_options capability on Solaris provider "sun" & "pkg" - clone
Title: Message Title Casey Williams assigned an issue to Casey Williams Puppet / PUP-5287 install_options capability on Solaris provider "sun" & "pkg" - clone 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. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1889) Windows operating system facts should resolve correctly for Server 2019
Title: Message Title Casey Williams assigned an issue to Unassigned Facter / FACT-1889 Windows operating system facts should resolve correctly for Server 2019 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. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1889) Windows operating system facts should resolve correctly for Server 2019
Title: Message Title Casey Williams assigned an issue to Casey Williams Facter / FACT-1889 Windows operating system facts should resolve correctly for Server 2019 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5759) Windows: Puppet agent doesn't create directory when parent is a mounted volume
Title: Message Title Casey Williams assigned an issue to Casey Williams Puppet / PUP-5759 Windows: Puppet agent doesn't create directory when parent is a mounted volume 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8735) File resource doesn't seem to parse UTF8 filenames when recursively copying directories
Title: Message Title Casey Williams assigned an issue to Casey Williams Puppet / PUP-8735 File resource doesn't seem to parse UTF8 filenames when recursively copying directories 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9111) Restarting services using launchd service provider is flaky
Title: Message Title Casey Williams updated an issue Puppet / PUP-9111 Restarting services using launchd service provider is flaky Change By: Casey Williams Fix Version/s: PUP 6.0.1 Fix Version/s: PUP 5.5.7 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-9044) Update puppet portage package provider for new output generated by qatom
Title: Message Title Casey Williams updated an issue Puppet / PUP-9044 Update puppet portage package provider for new output generated by qatom Change By: Casey Williams Fix Version/s: PUP 6.0.1 Fix Version/s: PUP 5.5.7 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-6569) Improve error messaging for Windows user management
Title: Message Title Casey Williams assigned an issue to Casey Williams Puppet / PUP-6569 Improve error messaging for Windows user management 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. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1644) facter on AIX doesn't set processors.physicalcount to anything
Title: Message Title Casey Williams assigned an issue to Branan Riley Facter / FACT-1644 facter on AIX doesn't set processors.physicalcount to anything Change By: Casey Williams Assignee: Branan Riley 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-7604) The AIX 'group' provider should not quote 'gid' (it is supposed to be numeric)
Title: Message Title Casey Williams commented on PUP-7604 Re: The AIX 'group' provider should not quote 'gid' (it is supposed to be numeric) This is addressed as part of a PR for PUP-9049 and PUP-3021 here 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-7533) User resource in AIX does not update attributes
Title: Message Title Casey Williams commented on PUP-7533 Re: User resource in AIX does not update attributes This is addressed as part of a PR for PUP-9049 and PUP-3021 here 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-7241) AIX - Errors when parsing lsuser output with special characters (#!)
Title: Message Title Casey Williams commented on PUP-7241 Re: AIX - Errors when parsing lsuser output with special characters (#!) This is addressed as part of a PR for PUP-9049 and PUP-3021 here 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-9064) Puppet assumes all SSL certs it verifies have client purpose set
Title: Message Title Casey Williams updated an issue Puppet / PUP-9064 Puppet assumes all SSL certs it verifies have client purpose set Change By: Casey Williams 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 (PUP-9064) Puppet assumes all SSL certs it verifies have client purpose set
Title: Message Title Casey Williams updated an issue Puppet / PUP-9064 Puppet assumes all SSL certs it verifies have client purpose set Change By: Casey Williams Priority: Normal 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9064) Puppet assumes all SSL certs it verifies have client purpose set
Title: Message Title
Casey Williams updated an issue
Puppet / PUP-9064
Puppet assumes all SSL certs it verifies have client purpose set
Change By:
Casey Williams
[This PR|https://github.com/puppetlabs/puppet/pull/6973] is open to update Travis & Appveyor to test puppet's master branch using ruby 2.5; The Appveyor tests have uncovered a legitimate puppet failure ([link to the full log here|https://ci.appveyor.com/project/puppetlabs/puppet/build/4.1.0.8733/job/bmcje50w2tvej3pw]):{code}Failures: 1) Puppet::Indirector::CertificateStatus::File when searching should return a list of all hosts with certificate requests, signed certs, or revoked certs Failure/Error: expect(results).to eq([["ca","signed"],["requested_host","requested"],["revoked_host","revoked"],["signed_host","signed"]]) expected: [["ca", "signed"], ["requested_host", "requested"], ["revoked_host", "revoked"], ["signed_host", "signed"]]got: [["ca", "revoked"], ["requested_host", "requested"], ["revoked_host", "revoked"], ["signed_host", "signed"]] (compared using ==) # ./spec/unit/indirector/certificate_status/file_spec.rb:188:in `block (3 levels) in ' # util/rspec_runner:44:in `run' # util/rspec_runner:59:in `'Finished in 49.26 seconds (files took 7.23 seconds to load){code}A summary of some discussion we've had around this in PRs and chat so far: * This happens with Ruby 2.5.x and and OpenSSL 1.1.0. We suspect we're seeing this failure in Appveyor and not Travis because Travis may build their Ruby 2.5.x against an earlier version of OpenSSL * We set purpose to SSL_CLIENT, and OpenSSL 1.1.0, unlike earlier versions, takes this as an indication that it should be checking the purpose during verification * This failure only manifests when verifying the CA using itself: ** This normally works because the CA is a self-signed cert ** But the CA does not have the SSL_CLIENT purpose, so it fails verification now * To fix this, we need to find some way not to set the purpose when verifying the CA cert using itself: ** We may add an optional purpose parameter to the [verify method|https://github.com/puppetlabs/puppet/blob/8ee569d00a3dd8664998ff89db75c7c16703e99e/lib/puppet/ssl/certificate_authority.rb#L495], and have it default to {{OpenSSL::X509::PURPOSE_SSL_CLIENT}}. Then, Host's state method could pass {{OpenSSL::PURPOSE_ANY}} [here|https://github.com/puppetlabs/puppet/blob/8ee569d00a3dd8664998ff89db75c7c16703e99e/lib/puppet/ssl/host.rb#L405].[~sean.mcdonald] provided [this script|https://gist.githubusercontent.com/McdonaldSeanp/3d92c654ee16acc37b590b3d5dac3fc2/raw/7c42eeffaebf391a38485a0b54911d7a021c1c5a/certificate_check.rb] to perform a test that creates a CA and attempts to verify it with and without the purpose set (requires system openssl installed).This issue blocks PUP-8614 (adding ruby 2.5 to puppet's Travis/Appveyor config), which blocks the upgrade to ruby 2.5.1 in puppet-agent.
Jira (PUP-9064) Puppet assumes all SSL certs it verifies have client purpose set
Title: Message Title Casey Williams created an issue Puppet / PUP-9064 Puppet assumes all SSL certs it verifies have client purpose set Issue Type: Bug Assignee: Unassigned Created: 2018/08/14 9:30 AM Fix Versions: PUP 6.0.0 Priority: Normal Reporter: Casey Williams This PR is open to update Travis & Appveyor to test puppet's master branch using ruby 2.5; The Appveyor tests have uncovered a legitimate puppet failure (link to the full log here): Failures: 1) Puppet::Indirector::CertificateStatus::File when searching should return a list of all hosts with certificate requests, signed certs, or revoked certs Failure/Error: expect(results).to eq([["ca","signed"],["requested_host","requested"],["revoked_host","revoked"],["signed_host","signed"]]) expected: [["ca", "signed"], ["requested_host", "requested"], ["revoked_host", "revoked"], ["signed_host", "signed"]]
Jira (PUP-9056) File type errors when statting paths with unrecognized characters on Windows with Ruby 2.5.1
Title: Message Title Casey Williams moved an issue Puppet / PUP-9056 File type errors when statting paths with unrecognized characters on Windows with Ruby 2.5.1 Change By: Casey Williams Method Found: Needs Assessment Issue Type: Bug Task Key: PA PUP - 2140 9056 Project: 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
Jira (FACT-1865) Amazon Linux 2 is reported as 4
Title: Message Title Casey Williams updated an issue Facter / FACT-1865 Amazon Linux 2 is reported as 4 Change By: Casey Williams Release Notes Summary: Updates facter to correctly read the format of /etc/system-release under Amazon Linux 2. This corrects the os release fact, which previously fell back to the kernel version. 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-1865) Amazon Linux 2 is reported as 4
Title: Message Title Casey Williams updated an issue Facter / FACT-1865 Amazon Linux 2 is reported as 4 Change By: Casey Williams 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 (FACT-1865) Amazon Linux 2 is reported as 4
Title: Message Title Casey Williams assigned an issue to Casey Williams Facter / FACT-1865 Amazon Linux 2 is reported as 4 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8970) Puppet cron acceptance tests should be skipped on Fedora 28
Title: Message Title Casey Williams created an issue Puppet / PUP-8970 Puppet cron acceptance tests should be skipped on Fedora 28 Issue Type: Task Assignee: Casey Williams Created: 2018/06/27 3:04 PM Fix Versions: PUP 5.5.z Labels: systemd cron type_and_provider fedora linux Priority: Normal Reporter: Casey Williams Fedora 28 does not ship with a crontab executable preinstalled (I assume that systemd timers are now the preferred way to handle scheduled tasks). This fails puppet's cron acceptance tests. Add Comment
Jira (FACT-1844) JDK 10 has removed javah breaking the build
Title: Message Title Casey Williams commented on FACT-1844 Re: JDK 10 has removed javah breaking the build Changes requested - moving to Needs Information for now. 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-1851) Linux networking resolver doesn't collect DHCP information under systemd-networkd
Title: Message Title Casey Williams updated an issue Facter / FACT-1851 Linux networking resolver doesn't collect DHCP information under systemd-networkd Change By: Casey Williams Release Notes Summary: Systems relying entirely on systemd-networkd for DHCP management do not use dhclient -- this checks systemd-networkd's DHCP leases directory (/run/systemd/netif/leases) in addition to dhclient's lease files when attempting to identify DHCP servers. 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-1851) Linux networking resolver doesn't collect DHCP information under systemd-networkd
Title: Message Title Casey Williams commented on FACT-1851 Re: Linux networking resolver doesn't collect DHCP information under systemd-networkd Apologies, Garrett Guillotte – missed kenn's note initially – I've added some notes 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-1851) Linux networking resolver doesn't collect DHCP information under systemd-networkd
Title: Message Title Casey Williams updated an issue Facter / FACT-1851 Linux networking resolver doesn't collect DHCP information under systemd-networkd Change By: Casey Williams 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 (FACT-620) windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms
Title: Message Title Casey Williams commented on FACT-620 Re: windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms Closing – per Eric Sorenson's reluctance, we feel the benefits of consistency here wouldn't outweigh the breakage across existing puppet code that this would cause. 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-1142) Facter FQDN resolution is incorrect on Windows
Title: Message Title Casey Williams updated an issue Facter / FACT-1142 Facter FQDN resolution is incorrect on Windows Change By: Casey Williams Sprint: Platform OS Ready for Eng. 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-1501) timezone contains wrong value
Title: Message Title Casey Williams updated an issue Facter / FACT-1501 timezone contains wrong value Change By: Casey Williams Labels: needs_repro timezo triaged windows Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1851) Linux networking resolver doesn't collect DHCP information under systemd-networkd
Title: Message Title Casey Williams updated an issue Facter / FACT-1851 Linux networking resolver doesn't collect DHCP information under systemd-networkd Change By: Casey Williams Fix Version/s: FACT 4.0.0 Fix Version/s: FACT 3.11.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 (FACT-1851) Linux networking resolver doesn't collect DHCP information under systemd-networkd
Title: Message Title Casey Williams updated an issue Facter / FACT-1851 Linux networking resolver doesn't collect DHCP information under systemd-networkd Change By: Casey Williams Summary: Linux networking resolver doesn't collect DHCP information under systemd-networkd 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-1851) Linux networking resolver doesn't collect DHCP information under systemd-networkd
Title: Message Title Casey Williams updated an issue Facter / FACT-1851 Linux networking resolver doesn't collect DHCP information under systemd-networkd Change By: Casey Williams Issue Type: Task 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 (FACT-1851) Linux networking resolver doesn't collect DHCP under systemd-networkd
Title: Message Title Casey Williams created an issue Facter / FACT-1851 Linux networking resolver doesn't collect DHCP under systemd-networkd Issue Type: Task Assignee: Casey Williams Created: 2018/05/03 4:39 PM Priority: Normal Reporter: Casey Williams When using the systemd-networkd DHCP client, the Linux networking resolver doesn't know how to collect DHCP lease information, since it expects dhclient to be installed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1851) Linux networking resolver doesn't collect DHCP under systemd-networkd
Title: Message Title Casey Williams updated an issue Facter / FACT-1851 Linux networking resolver doesn't collect DHCP under systemd-networkd Change By: Casey Williams Sprint: Platform OS 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 (FACT-1847) Implement "cloud" fact Azure identification for Windows platform
Title: Message Title Casey Williams assigned an issue to Casey Williams Facter / FACT-1847 Implement "cloud" fact Azure identification for Windows platform 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. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1768) libwhereami uses deprecated syntax
Title: Message Title Casey Williams updated an issue Facter / FACT-1768 libwhereami uses deprecated syntax Change By: Casey Williams Fix Version/s: FACT 3.11.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 (FACT-1785) Add device-tree data source to libwhereami
Title: Message Title Casey Williams updated an issue Facter / FACT-1785 Add device-tree data source to libwhereami Change By: Casey Williams Labels: triaged virtualization 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-1795) Add whereami executable
Title: Message Title Casey Williams updated an issue Facter / FACT-1795 Add whereami executable Change By: Casey Williams Labels: triaged virtualization 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-1795) Add whereami executable
Title: Message Title Casey Williams updated an issue Facter / FACT-1795 Add whereami executable Change By: Casey Williams Component/s: libwhereami 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-1668) Add support for parallels virtualization detection
Title: Message Title Casey Williams updated an issue Facter / FACT-1668 Add support for parallels virtualization detection Change By: Casey Williams Labels: triaged virtualization 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-1669) Add support for zlinux virtualization detection
Title: Message Title Casey Williams updated an issue Facter / FACT-1669 Add support for zlinux virtualization detection Change By: Casey Williams Labels: triaged virtualization 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-1669) Add support for zlinux virtualization detection
Title: Message Title Casey Williams updated an issue Facter / FACT-1669 Add support for zlinux virtualization detection Change By: Casey Williams Component/s: libwhereami 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-1669) Add support for zlinux virtualization detection
Title: Message Title Casey Williams updated an issue Facter / FACT-1669 Add support for zlinux virtualization detection Change By: Casey Williams Fix Version/s: FACT 3.y Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1662) Add support for vserver virtualization detection
Title: Message Title Casey Williams updated an issue Facter / FACT-1662 Add support for vserver virtualization detection Change By: Casey Williams Labels: triaged virtualization 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.
