Jira (PDB-5553) Remove foreign keys from report partitions
Title: Message Title Sean McDonald updated an issue PuppetDB / PDB-5553 Remove foreign keys from report partitions Change By: Sean McDonald Sprint: Skeletor 11/23/2022, Skeletor 12/07/2022 , Skeletor 12/21/2022 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472747.1666299762000.64658.1670436360337%40Atlassian.JIRA.
Jira (PUP-11683) Tasks are unable to be listed when a single task in an environment has malformed metadata
Title: Message Title Sean McDonald updated an issue Puppet / PUP-11683 Tasks are unable to be listed when a single task in an environment has malformed metadata Change By: Sean McDonald Sprint: Skeletor 12/07/2022 , Skeletor 12/21/2022 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.474434.1668124207000.64656.1670436360237%40Atlassian.JIRA.
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Sean McDonald updated an issue PuppetDB / PDB-5554 Remove partitions in a non-world-blocking way Change By: Sean McDonald Sprint: Skeletor 11/09/2022, Skeletor 11/23/2022, Skeletor 12/07/2022 , Skeletor 12/21/2022 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.472748.1666300333000.64657.1670436360285%40Atlassian.JIRA.
Jira (PDB-5557) Enable drop-joins for subqueries
Title: Message Title Sean McDonald updated an issue PuppetDB / PDB-5557 Enable drop-joins for subqueries Change By: Sean McDonald Sprint: Skeletor 12/07/2022 , Skeletor 12/21/2022 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.473181.127979000.64660.1670436360438%40Atlassian.JIRA.
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Sean McDonald updated an issue PuppetDB / PDB-5567 Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions Change By: Sean McDonald Sprint: Skeletor 12/07/2022 , Skeletor 12/21/2022 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.475715.1669757045000.64659.1670436360389%40Atlassian.JIRA.
Jira (PUP-11002) Expose v4 catalog endpoint for {{Puppet::HTTP::Service::Compiler}}
Title: Message Title
Sean McDonald updated an issue
Puppet / PUP-11002
Expose v4 catalog endpoint for {{Puppet::HTTP::Service::Compiler}}
Change By:
Sean McDonald
Sprint:
Skeletor Ready to groom
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.393513.161723397.179526.1617288240613%40Atlassian.JIRA.
Jira (PUP-10476) Update Puppet's PAL API to fulfill bolt use cases
Title: Message Title Sean McDonald updated an issue Puppet / PUP-10476 Update Puppet's PAL API to fulfill bolt use cases Change By: Sean McDonald Sprint: Skeletor 5/6/2020 , Skeletor 5/20/2020 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.357007.1588086087000.56122.1588791720051%40Atlassian.JIRA.
Jira (PUP-10476) Update Puppet's PAL API to fulfill bolt use cases
Title: Message Title Sean McDonald updated an issue Puppet / PUP-10476 Update Puppet's PAL API to fulfill bolt use cases Change By: Sean McDonald Sprint: Skeletor 5/6/2020 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.357007.1588086087000.53224.1588361640043%40Atlassian.JIRA.
Jira (PUP-10476) Update Puppet's PAL API to fulfill bolt use cases
Title: Message Title Sean McDonald commented on PUP-10476 Re: Update Puppet's PAL API to fulfill bolt use cases This is assigned to me for now. This work was spawned from conversations around the compile API in puppetserver and changes we needed to support apply blocks in plans: https://github.com/puppetlabs/puppetserver/pull/2329#discussion_r416030694 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.357007.1588086087000.48776.1588087320024%40Atlassian.JIRA.
Jira (PUP-10476) Update Puppet's PAL API to fulfill bolt use cases
Title: Message Title Sean McDonald created an issue Puppet / PUP-10476 Update Puppet's PAL API to fulfill bolt use cases Issue Type: Task Assignee: Sean McDonald Created: 2020/04/28 8:01 AM Priority: Normal Reporter: Sean McDonald Update the PAL implementation to support newer use cases in bolt. There are a few cases in bolt's code where we are calling private functions in the compile layer to override some settings. At least two examples: one when filtering variables and another when evaluating to get node definitions Bolt also overrides some puppet settings, like rich data. The PAL layer in puppet should be updated to handle these cases and have sane defaults, such that we don't need to call private or internal functions in bolt (or PE when it's using bolt) or update puppet settings to compile correctly. Add Comment
Jira (PUP-10265) Add 'site-modules' to the environment default modulepath
Title: Message Title
Sean McDonald updated an issue
Puppet / PUP-10265
Add 'site-modules' to the environment default modulepath
Change By:
Sean McDonald
By default, an environment's modulepath does not contain {{site-modules}}. In bolt, that is a default path available to bolt projects, and when users want to migrate their bolt projects to PE it would be nice if the defaults default modulepaths were the same.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.344733.1580758475000.11492.1580758560123%40Atlassian.JIRA.
Jira (PUP-10265) Add 'site-modules' to the environment default modulepath
Title: Message Title
Sean McDonald updated an issue
Puppet / PUP-10265
Add 'site-modules' to the environment default modulepath
Change By:
Sean McDonald
By default, an environment's modulepath does not contain {{site-modules}}. In bolt, that is a default path available to Boltdirs bolt projects , and when users want to migrate their bolt projects to PE it would be nice if the defaults modulepaths were the same.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.344733.1580758475000.11491.1580758560081%40Atlassian.JIRA.
Jira (PUP-10265) Add 'site-modules' to the environment default modulepath
Title: Message Title
Sean McDonald updated an issue
Puppet / PUP-10265
Add 'site-modules' to the environment default modulepath
Change By:
Sean McDonald
By default, an environment's modulepath does not contain { { site-modules} } . In bolt, that is a default path available to Boltdirs, and when users want to migrate their bolt projects to PE it would be nice if the defaults modulepaths were the same.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.344733.1580758475000.11490.1580758500187%40Atlassian.JIRA.
Jira (PUP-10265) Add 'site-modules' to the environment default modulepath
Title: Message Title
Sean McDonald created an issue
Puppet / PUP-10265
Add 'site-modules' to the environment default modulepath
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2020/02/03 11:34 AM
Priority:
Normal
Reporter:
Sean McDonald
By default, an environment's modulepath does not contain {site-modules} . In bolt, that is a default path available to Boltdirs, and when users want to migrate their bolt projects to PE it would be nice if the defaults modulepaths were the same.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8318) Allow client tools and classifier gem to support parameters
Title: Message Title Sean McDonald commented on PUP-8318 Re: Allow client tools and classifier gem to support parameters I'm going to close this due to inactivity. Go ahead and re-open if this is still important. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.229070.1515102987000.11096.1580752680523%40Atlassian.JIRA.
Jira (BOLT-1468) Add 'check-node-connections' endpoint in bolt-server to support wait_until_available
Title: Message Title
Sean McDonald updated an issue
Puppet Task Runner / BOLT-1468
Add 'check-node-connections' endpoint in bolt-server to support wait_until_available
Change By:
Sean McDonald
*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.ORCH-2321 describes process of enabling "wait until available" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "wait until available" when there is no PCP transport available.**NOTE** the implementation of connection checks for wait until available is different from other bolt actions! Due to the nature of wait_until_available the bolt-server endpoint will *_not_* perform the same operation as an actual "wait_until_available" call. The differences are as follows:# Orchestrator will be performing the actual process of 'waiting' for nodes to be connected, so the endpoint in bolt-server *_should not wait_*. The bolt-server endpoint should check for the status of all node connections and then return immediately.# Node checks from the orchestrator are performed in batches, not one target at a time. The schema and implementation for checking connections in bolt server should expect an array of nodes to check.*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 "check connected nodes" 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 checking node connections via SSH and WinRM, using the new JSON schema. * Document the new endpoints in the
Jira (BOLT-1468) Add 'check-node-connections' endpoint in bolt-server to support wait_until_available
Title: Message Title Sean McDonald updated an issue Puppet Task Runner / BOLT-1468 Add 'check-node-connections' endpoint in bolt-server to support wait_until_available Change By: Sean McDonald Summary: implement wait_until_available Add 'check-node-connections' endpoint in bolt-server to support wait_until_available Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315953.1562789343000.74244.1566923640248%40Atlassian.JIRA.
Jira (BOLT-1468) Add 'check-node-connections' endpoint in bolt-server to support wait_until_available
Title: Message Title
Sean McDonald updated an issue
Puppet Task Runner / BOLT-1468
Add 'check-node-connections' endpoint in bolt-server to support wait_until_available
Change By:
Sean McDonald
*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-2321 describe describes process of enabling "wait until available" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "wait until available" when there is no PCP transport available.**NOTE** the implementation of connection checks for wait until available is different from other bolt actions! Due to the nature of wait_until_available the bolt-server endpoint will *_not_* perform the same operation as an actual "wait_until_available" call. The differences are as follows:# Orchestrator will be performing the actual process of 'waiting' for nodes to be connected, so the endpoint in bolt-server *_should not wait_*. The bolt-server endpoint should check for the status of all node connections and then return immediately.# Node checks from the orchestrator are performed in batches, not one target at a time. The schema and implementation for checking connections in bolt server should expect an array of nodes to check.*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 "check connected nodes" 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 checking node connections via SSH and WinRM, using the new JSON schema. * Document the
Jira (BOLT-1468) implement wait_until_available in bolt-server
Title: Message Title
Sean McDonald updated an issue
Puppet Task Runner / BOLT-1468
implement wait_until_available in bolt-server
Change By:
Sean McDonald
Bolt *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 needs " 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-2321 describe process of enabling "wait until available" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "wait until available" when there is no PCP transport available.**NOTE** the implementation of [ connection checks for wait until available is different from other bolt actions! Due to the nature of wait_until_available the bolt-server endpoint will *_not_* perform the same operation as an actual "wait_until_available" call. The differences are as follows:# Orchestrator will be performing the actual process of 'waiting' for nodes to be connected, so the endpoint in bolt-server *_should not wait_*. The bolt-server endpoint should check for the status of all node connections and then return immediately.# Node checks from the orchestrator are performed in batches, not one target at a time. The schema and implementation for checking connections in bolt server should expect an array of nodes to check.*Requirements*Changes will be made to the [bolt server app |https:// puppet github .com/ docs puppetlabs /bolt/ latest tree / plan_functions master/lib/bolt_server]: * The app follows the [json schema specification|https://json-schema . org/specification. html #wait-until-available ] . Add a description of the JSON schema for orchestrator data passed to use when the SSH or WinRM transports are used new endpoints [here|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server/schemas]. This schema should match the one defined for nodes not the "check connected to nodes" action in PCP -868 . As an example, Implementation of the run_task endpoint is available * Add new POST endpoints in the [ transport
Jira (BOLT-1468) implement wait_until_available in bolt-server
Title: Message Title Sean McDonald assigned an issue to Unassigned Puppet Task Runner / BOLT-1468 implement wait_until_available in bolt-server Change By: Sean McDonald Assignee: Sean McDonald Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315953.1562789343000.72322.1566840360091%40Atlassian.JIRA.
Jira (BOLT-1468) implement wait_until_available in bolt-server
Title: Message Title Sean McDonald assigned an issue to Sean McDonald Puppet Task Runner / BOLT-1468 implement wait_until_available in bolt-server Change By: Sean McDonald Assignee: Sean McDonald Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315953.1562789343000.72076.1566834900072%40Atlassian.JIRA.
Jira (BOLT-1401) Add 'upload_file' endpoint to bolt-server
Title: Message Title Sean McDonald updated an issue Puppet Task Runner / BOLT-1401 Add 'upload_file' endpoint to bolt-server Change By: Sean McDonald Sprint: Skeletor Kanban 20190814 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312870.1560800684000.49370.1565305200289%40Atlassian.JIRA.
Jira (BOLT-1402) Add 'run_script' endpoint to bolt-server
Title: Message Title Sean McDonald updated an issue Puppet Task Runner / BOLT-1402 Add 'run_script' endpoint to bolt-server Change By: Sean McDonald Sprint: Skeletor Kanban 20190814 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312873.1560801019000.49372.1565305200387%40Atlassian.JIRA.
Jira (BOLT-1468) implement wait_until_available in bolt-server
Title: Message Title Sean McDonald updated an issue Puppet Task Runner / BOLT-1468 implement wait_until_available in bolt-server Change By: Sean McDonald Sprint: Skeletor Kanban 20190717 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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.315953.1562789343000.11742.1562799660058%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1468) implement wait_until_available in bolt-server
Title: Message Title Sean McDonald moved an issue Puppet Task Runner / BOLT-1468 implement wait_until_available in bolt-server Change By: Sean McDonald Key: ORCH BOLT - 2324 1468 Project: Orchestration Puppet Task Runner Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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.315953.1562789343000.11740.1562799480057%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title Sean McDonald assigned an issue to Unassigned Puppet Task Runner / BOLT-1400 Add 'run_command' endpoint to bolt-server Change By: Sean McDonald Assignee: Casey Williams Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.5594.1562179560117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title Sean McDonald updated an issue Puppet Task Runner / BOLT-1400 Add 'run_command' endpoint to bolt-server Change By: Sean McDonald Sprint: Skeletor Kanban 20190619 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.49994.1560801360656%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title Sean McDonald assigned an issue to Casey Williams Puppet Task Runner / BOLT-1400 Add 'run_command' endpoint to bolt-server Change By: Sean McDonald Assignee: Casey Williams Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.49996.1560801360750%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9722) Regression: File mode changed on every puppet run
Title: Message Title Sean McDonald commented on PUP-9722 Re: Regression: File mode changed on every puppet run Ping Mihai Buzgau on this ticket. I've assigned it to your team and added it to your PR triage. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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.310253.1558976203000.22545.1559064420997%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9722) Regression: File mode changed on every puppet run
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9722 Regression: File mode changed on every puppet run Change By: Sean McDonald Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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.310253.1558976203000.22541.1559064420810%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9722) Regression: File mode changed on every puppet run
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9722 Regression: File mode changed on every puppet run Change By: Sean McDonald Team: Platform OS 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310253.1558976203000.22538.1559064420706%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Sean McDonald commented on PUP-9337 Re: Puppet sets permissions for Puppet files every run https://tickets.puppetlabs.com/browse/PE-26477 has been created to track this work in the PE space. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Sean McDonald commented on PUP-9337 Re: Puppet sets permissions for Puppet files every run yeah, I will work on it with her Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-1881) Include additional OS release facts for Windows 10
Title: Message Title Sean McDonald commented on FACT-1881 Re: Include additional OS release facts for Windows 10 Mihai Buzgau we've seen a question from Support recently on this feature ticket, so I've assigned it directly to your team and put it in the triage sprint. I also copied you on the email thread with the support question for more context. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-1881) Include additional OS release facts for Windows 10
Title: Message Title Sean McDonald updated an issue Facter / FACT-1881 Include additional OS release facts for Windows 10 Change By: Sean McDonald Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-1881) Include additional OS release facts for Windows 10
Title: Message Title Sean McDonald updated an issue Facter / FACT-1881 Include additional OS release facts for Windows 10 Change By: Sean McDonald Team: Platform OS 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 (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Sean McDonald Release Notes Summary: Puppet will now treat owner and group on the file resource as in-sync in the following scenario:* owner / and group are not set in the resource* owner and / or group are set to the SYSTEM user on the running node. * the SYSTEM user ACE is set to Full ControlPuppet will allow users to specifically configure the SYSTEM user to less than FullControl by setting the owner and/or group parameters to 'SYSTEM' in the file resource. (i.e. if owner and/or group are set to 'SYSTEM' puppet will _not_ munge permissions to FullControl). In this case Puppet will emit a warning since setting SYSTEM to less than FullControl may have unintended consequences. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Sean McDonald Release Notes Summary: Puppet will now treat owner and group on the file resource as in-sync in the following scenario:* owner/group are not set in the resource* owner/group are set to the SYSTEM user* the SYSTEM user ACE is set to Full ControlPuppet will allow users to specifically configure the SYSTEM user to less than FullControl by setting the owner and/or group parameters to 'SYSTEM' in the file resource. (i.e. if owner and/or group are set to 'SYSTEM' puppet will _not_ munge permissions to FullControl). In this case Puppet will emit a warning since setting SYSTEM to less than FullControl may have unintended consequences. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Sean McDonald Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Sean McDonald assigned an issue to Unassigned Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Sean McDonald Assignee: Sean McDonald Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Sean McDonald Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-1884) Add NIM master detection
Title: Message Title Sean McDonald updated an issue Facter / FACT-1884 Add NIM master detection Change By: Sean McDonald Team: Platform OS 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 (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Sean McDonald Team: Platform OS 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-1884) Add NIM master detection
Title: Message Title Sean McDonald updated an issue Facter / FACT-1884 Add NIM master detection Change By: Sean McDonald Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Sean McDonald Fix Version/s: PUP 6.0.6 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 (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Sean McDonald commented on PUP-9337 Re: Puppet sets permissions for Puppet files every run Kenn Hussey yeah, the PR is meant as a fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Sean McDonald assigned an issue to Sean McDonald Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Sean McDonald Assignee: Sean McDonald Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Sean McDonald Team: Windows Platform OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Sean McDonald Sprint: Windows Hopper 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-9150) cwd option in Puppet::Util::Execution.execute should work with different Windows path types
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9150 cwd option in Puppet::Util::Execution.execute should work with different Windows path types Change By: Sean McDonald Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1346) Provide Environment Variables as a Structured Fact
Title: Message Title Sean McDonald commented on FACT-1346 Re: Provide Environment Variables as a Structured Fact Since this seems solved in modules we would prefer to keep actual fact implementation out of the core facter implementation and inside modules. If we can build the important windows env vars in to a module we could even include that module with the core set of modules that ship 'batteries included' with the agent. If anyone disagrees, please feel free to re-open this ticket with reasoning on why it's important that this stay in core facter. /cc 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-1898) Provide core facts or supported module with common Windows paths
Title: Message Title Sean McDonald commented on FACT-1898 Re: Provide core facts or supported module with common Windows paths Since this seems solved in modules we would prefer to keep actual fact implementation out of the core facter implementation and inside modules. If we can build the important windows env vars in to a module we could even include that module with the core set of modules that ship 'batteries included' with the agent. If anyone disagrees, please feel free to re-open this ticket with reasoning on why it's important that this stay in core facter. /cc 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-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Sean McDonald commented on PUP-8002 Re: "Attempt to redefine entity" caused by using a resource collector Yes, it can Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9339) Refreshed resources do not get a status event in the report
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9339 Refreshed resources do not get a status event in the report Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9330) Unable to enfource SELinux attributes for files in /dev/shm
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9330 Unable to enfource SELinux attributes for files in /dev/shm Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9326) Support for systemd on Linux Mint 18 & 19
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9326 Support for systemd on Linux Mint 18 & 19 Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9340) Failing spec test in puppet travis testing
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9340 Failing spec test in puppet travis testing Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9318) Fixup puppet device to correctly pluginsync and only put pluginsyncdest on the LOAD_PATH
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9318 Fixup puppet device to correctly pluginsync and only put pluginsyncdest on the LOAD_PATH Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9317) Backport PUP-8002 to 5.5.x ("Attempt to redefine entity")
Title: Message Title
Sean McDonald updated an issue
Puppet / PUP-9317
Backport PUP-8002 to 5.5.x ("Attempt to redefine entity")
Change By:
Sean McDonald
Fix Version/s:
PUP 6.1.0
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9319) fix --environment handling
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9319 fix --environment handling Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9294) Raise Error when a legacy function illegally defines methods
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9294 Raise Error when a legacy function illegally defines methods Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9312) puppet package provider fails when reading from registry
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9312 puppet package provider fails when reading from registry Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9293) read_wide_string hides errors if the string is nil
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9293 read_wide_string hides errors if the string is nil Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9310) Timespan and Timestamp types cannot be specified from integer or float
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9310 Timespan and Timestamp types cannot be specified from integer or float Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9248) add support for devices to puppet ssl
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9248 add support for devices to puppet ssl Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9292) use-after-free in windows service utils
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9292 use-after-free in windows service utils Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9294) Raise Error when a legacy function illegally defines methods
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9294 Raise Error when a legacy function illegally defines methods Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9240) Solaris SMF service has to support non global zone
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9240 Solaris SMF service has to support non global zone Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9217) Crontab gets erased after error during agent run
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9217 Crontab gets erased after error during agent run Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9356) `puppet device` does not load local plugins for --apply --facts and --resource
Title: Message Title Sean McDonald commented on PUP-9356 Re: `puppet device` does not load local plugins for --apply --facts and --resource Kenn Hussey we'll be performing mergups today to ensure 5.5 / 6.0 changes land in 6.1, so yes Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9113) Unable to manage services with what looks like HyperV installed on Windows
Title: Message Title Sean McDonald commented on PUP-9113 Re: Unable to manage services with what looks like HyperV installed on Windows This is fixed in puppet 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-9113) Unable to manage services with what looks like HyperV installed on Windows
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9113 Unable to manage services with what looks like HyperV installed on Windows Change By: Sean McDonald 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-9340) Failing spec test in puppet travis testing
Title: Message Title
Sean McDonald created an issue
Puppet / PUP-9340
Failing spec test in puppet travis testing
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/12/05 10:19 AM
Priority:
Normal
Reporter:
Sean McDonald
example job: https://travis-ci.org/puppetlabs/puppet/jobs/463959473 failure:
1) Puppet::Indirector::Yaml when searching should return an array of fact instances with one instance for each file when globbing *
Failure/Error: expect(terminus.search(request)).to eq([one, two])
expected: [{"name"=>"one", "values"=>{"foo"=>"bar"}}, {"name"=>"two", "values"=>{"foo"=>"baz"}}]
got: [{"name"=>"two", "values"=>{"foo"=>"baz"}}, {"name"=>"one", "values"=>{"foo"=>"bar"}}]
(compared using ==)
Diff:
Jira (PUP-9298) Update directory? check on cwd in Execution.execute
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9298 Update directory? check on cwd in Execution.execute Change By: Sean McDonald Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9298) Update directory? check on cwd in Execution.execute
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9298 Update directory? check on cwd in Execution.execute Change By: Sean McDonald 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-9298) Update directory? check on cwd in Execution.execute
Title: Message Title Sean McDonald created an issue Puppet / PUP-9298 Update directory? check on cwd in Execution.execute Issue Type: Task Assignee: Unassigned Created: 2018/11/01 10:14 AM Priority: Normal Reporter: Sean McDonald Puppet::Util::Execution.execute checks for the existence of the cwd specified when the :cwd option is given using Puppet::FileSystem.directory? However, Puppet::FileSystem.directory? currently can return a false negative with reparse points (symlinks) in windows. We should refactor that function so it works with reparse points. A change to refactor Puppet::FileSystem.dirctory? is likely too risky to introduce in a Z release, so we'll need to introduce two fixes: one that's safer for Z releases and one to actually fix Puppet::FileSystem.directory? Note that Puppet::Util::Windows::File.exist? works for directories as well (the underlying windows API used in that function is for files or directories), so that's likely the solution here: For the Z release streams we can simply have the check cwd use Puppet::Util::Windows::File.exist? on windows and directory? everywhere else. Then the change to the master branch should be to actually leverage Puppet::Util::Windows::File.exist? inside the windows specific Puppet::FileSystem.dirctory? Add Comment
Jira (PUP-9292) use-after-free in windows service utils
Title: Message Title Sean McDonald commented on PUP-9292 Re: use-after-free in windows service utils Nevermind, I forgot you don't need to clone or dup integers. You can still reproduce the use-after-free scenario if someone tries to return the reference to the object yielded inside the queries (or if someone tries to assign the pointers returned for the string values from the config query). These are unlikely scenarios and we should probably be fine. I do still think that the first option is handy because the string values for the config query will already be pulled in to ruby strings so any functions that call query won't need to do that. Plus the first change requires less code to work. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9292) use-after-free in windows service utils
Title: Message Title Sean McDonald commented on PUP-9292 Re: use-after-free in windows service utils There's two PRs open to fix this: One that copies the return values to ruby memory: https://github.com/puppetlabs/puppet/pull/7213 and another that changes the service query functions to execute blocks and yield the returned values: https://github.com/puppetlabs/puppet/pull/7214 The second option leaves open the possibility to reproduce the use-after-free scenario if in the future other functions make use of the service query functions and assign the values in the returned structs to variables meant to exist outside the blocks given to the query functions. You can assign the values to variables, but you must use .dup or .clone when doing so, otherwise you'll be right back in use-after-free land. Forgetting about .dup/.clone is easy, and I believe makes it easy to recreate this scenario. The first option however will make more garbage for the GC to collect. Though IMO in context it doesn't seem like that much: status queries would be the ones returning all the garbage, and they would only return a hash with 9 integers which seems pretty small to me. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9292) use-after-free in windows service utils
Title: Message Title Sean McDonald created an issue Puppet / PUP-9292 use-after-free in windows service utils Issue Type: Bug Affects Versions: PUP 6.0.3, PUP 5.5.6 Assignee: Sean McDonald Created: 2018/10/30 11:22 AM Fix Versions: PUP 5.5.8, PUP 6.0.5 Priority: Normal Reporter: Sean McDonald The windows service utils have a use-after-free failure in the query functions Add Comment
Jira (PUP-9150) cwd option in Puppet::Util::Execution.execute should work with different Windows path types
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9150 cwd option in Puppet::Util::Execution.execute should work with different Windows path types Change By: Sean McDonald Fix Version/s: PUP 6.0.5 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9150) cwd option in Puppet::Util::Execution.execute should work with different Windows path types
Title: Message Title Sean McDonald commented on PUP-9150 Re: cwd option in Puppet::Util::Execution.execute should work with different Windows path types Enis Inan I don't think CreateProcess actually has a security issue. It appears that CreateProcess won't fail when starting in the directory, but as soon as any operation is executed on the directory it will fail. technically it appears you would be inside the directory when CreateProcess starts, but you don't have access to anything inside it, you can't navigate within the directory (i.e. if there are other dirs inside the dir in question you can't access them), and you can't copy anything in or out. I've run a few tests and it appears windows will let you list your cwd, which wouldn't violate any security rules, because you can still view the existence of the top folder you can't access. However if you attempt any operations inside a nested dir (i.e. a dir you know exists but you don't have access to it's parent or itself) the operations will fail. I think in this scenario we can stick to just setting :cwd directly with CreateProcess and let that fail. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9150) cwd option in Puppet::Util::Execution.execute should work with different Windows path types
Title: Message Title Sean McDonald assigned an issue to Sean McDonald Puppet / PUP-9150 cwd option in Puppet::Util::Execution.execute should work with different Windows path types Change By: Sean McDonald Assignee: Enis Inan Sean McDonald Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9132) Create a configurable timeout for managed windows services
Title: Message Title
Sean McDonald updated an issue
Puppet / PUP-9132
Create a configurable timeout for managed windows services
Change By:
Sean McDonald
Release Notes Summary:
On windows: you can now specify a new parameter "timeout" that will create a minimum timeout in seconds for puppet to wait when syncing service properties. {code} service { "service-name": enable => true, ensure => running, timeout => 45} {code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9132) Create a configurable timeout for managed windows services
Title: Message Title
Sean McDonald updated an issue
Puppet / PUP-9132
Create a configurable timeout for managed windows services
Change By:
Sean McDonald
Release Notes Summary:
On windows: you can now specify a new parameter "timeout" that will create a minimum timeout in seconds for puppet to wait when syncing service properties. {code} service { "service-name": enable => true, ensure => running, timeout => 45} {code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9132) Create a configurable timeout for managed windows services
Title: Message Title
Sean McDonald updated an issue
Puppet / PUP-9132
Create a configurable timeout for managed windows services
Change By:
Sean McDonald
Release Notes Summary:
On windows: you can now specify a new parameter "timeout" that will create a minimum timeout in seconds for puppet to wait when syncing service properties.service { "service-name": enable => true, timeout => 45}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-9132) Create a configurable timeout for managed windows services
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9132 Create a configurable timeout for managed windows services Change By: Sean McDonald Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9132) Create a configurable timeout for managed windows services
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9132 Create a configurable timeout for managed windows services Change By: Sean McDonald Fix Version/s: PUP 6.1.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9132) Create a configurable timeout for managed windows services
Title: Message Title Sean McDonald assigned an issue to Sean McDonald Puppet / PUP-9132 Create a configurable timeout for managed windows services Change By: Sean McDonald Assignee: Sean McDonald Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6920) Windows package provider should set working directory (cwd)
Title: Message Title Sean McDonald updated an issue Puppet / PUP-6920 Windows package provider should set working directory (cwd) Change By: Sean McDonald Release Notes Summary: Package installations using the windows package provider will now perform installations in the same location as the 'source' attribute of the resource. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6920) Windows package provider should set working directory (cwd)
Title: Message Title Sean McDonald updated an issue Puppet / PUP-6920 Windows package provider should set working directory (cwd) Change By: Sean McDonald Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8351) PA-437 fix causes pip provider failures when SCL version is installed
Title: Message Title Sean McDonald assigned an issue to Sean McDonald Puppet / PUP-8351 PA-437 fix causes pip provider failures when SCL version is installed Change By: Sean McDonald Assignee: Sean McDonald Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-8351) PA-437 fix causes pip provider failures when SCL version is installed
Title: Message Title Sean McDonald commented on PUP-8351 Re: PA-437 fix causes pip provider failures when SCL version is installed Branan Riley when you source /opt/rh/python27/enable in to the profile the location of SCL python will precede the system python in PATH. Here is PATH before: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin Here is PATH after running source /opt/rh/python27/enable: PATH=/opt/rh/python27/root/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin and sure enough, running "which python" or "which pip" will return binaries for the SCL python/pip Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9150) cwd option in Puppet::Util::Execution.execute should work with different Windows path types
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9150 cwd option in Puppet::Util::Execution.execute should work with different Windows path types Change By: Sean McDonald 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-9193) puppet ignores exit code from windows exe package install because it uses 'start'
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9193 puppet ignores exit code from windows exe package install because it uses 'start' Change By: Sean McDonald 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-9193) puppet ignores exit code from windows exe package install because it uses 'start'
Title: Message Title Sean McDonald assigned an issue to Sean McDonald Puppet / PUP-9193 puppet ignores exit code from windows exe package install because it uses 'start' Change By: Sean McDonald Assignee: Sean McDonald Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6920) Windows package provider should set working directory (cwd)
Title: Message Title Sean McDonald commented on PUP-6920 Re: Windows package provider should set working directory (cwd) Blocked during 6.0.2 release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9193) puppet ignores exit code from windows exe package install because it uses 'start'
Title: Message Title Sean McDonald created an issue Puppet / PUP-9193 puppet ignores exit code from windows exe package install because it uses 'start' Issue Type: Bug Assignee: Unassigned Created: 2018/10/02 9:18 AM Environment: Windows (all versions) Labels: windows type_and_provider package Priority: Normal Reporter: Sean McDonald This effects all supported versions of puppet: We use "cmd /c start" to execute exe package installs on Windows: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/windows/exe_package.rb#L45. Comments suggest this is because otherwise executables that are console apps will launch a new window (which is undesired). However, the use of "start" means the calling process (i.e. puppet) will never see the actual exit code from the installation, only the exit code from the call to start (which will be 0: success) This means from puppet's perspective exe package installs always succeed and puppet will always report a successful installation, regardless of whether or not the application install actually succeeded.
Jira (PUP-9177) Add userflag support to Windows::ADSI::User
Title: Message Title Sean McDonald assigned an issue to Enis Inan Puppet / PUP-9177 Add userflag support to Windows::ADSI::User Change By: Sean McDonald Assignee: Enis Inan Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9177) Add userflag support to Windows::ADSI::User
Title: Message Title Sean McDonald created an issue Puppet / PUP-9177 Add userflag support to Windows::ADSI::User Issue Type: Task Assignee: Unassigned Created: 2018/09/25 2:52 PM Priority: Normal Reporter: Sean McDonald Add support for getting/setting ADSI userflags in Windows::ADSI::User This will facilitate work for changes required in PUP-5216 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-6920) Windows package provider should set working directory (cwd)
Title: Message Title Sean McDonald assigned an issue to Sean McDonald Puppet / PUP-6920 Windows package provider should set working directory (cwd) Change By: Sean McDonald Assignee: Sean McDonald Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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.
