Jira (PUP-9570) Catalog failure on first run due to pluginsync and environment switch
Title: Message Title Mike Smith commented on PUP-9570 Re: Catalog failure on first run due to pluginsync and environment switch ExxonMobil is currently encountering this bug. 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.300842.1553021716000.128438.1611943200159%40Atlassian.JIRA.
Jira (BOLT-1541) Bolt docs improvement regarding example code
Title: Message Title Mike Smith created an issue Puppet Task Runner / BOLT-1541 Bolt docs improvement regarding example code Issue Type: Improvement Assignee: Unassigned Components: bolt, DOCS Created: 2020/03/09 3:38 PM Priority: Normal Reporter: Mike Smith Any time there is an example of code for a given bolt workflow, feature, function, or best practice there should be an example in each common scripting language. Currently there is often only a ruby example. Most operations teams that would attempt to on-board bolt would not typically write administrative scripts in ruby but already have them in bash, powershell, or python. Given each of these options it will be make the on-boarding and first experience with Bolt more user friendly. Current pain point is with error handling for bash. The docs give ruby examples for error handling https://puppet.com/docs/bolt/latest/writing_tasks.html#returning-errors-in-tasks however I would need now look up error handling in bash to modify my code, then guess how to wrap that for a Bolt task specifically. Add Comment
Jira (BOLT-1540) Exit code handling in Tasks
Title: Message Title Mike Smith created an issue Puppet Task Runner / BOLT-1540 Exit code handling in Tasks Issue Type: Improvement Assignee: Unassigned Components: bolt Created: 2020/03/09 3:32 PM Labels: bolt Priority: Normal Reporter: Mike Smith The experience of users in a Walmart Bolt workshop found users experimenting with error handling. The group was very Ansible friendly and comparing features 1:1. They are mostly CLI users without access to enterprise tooling. They took a script and changed a command within the script to intentionally be wrong. Bolt script run - errors out. Bolt task run - success (no error). This experience is different than Ansible in that it will fail in both cases if the underlying script is bad. The Puppet docs mention "error handing" in tasks, but don't explain that is required to get error information https://puppet.com/docs/bolt/latest/writing_tasks.html#returning-errors-in-tasks . The expected behavior is that if a script fails a task that runs that script will also fail without introducing new code to handle specific errors.
Jira (BOLT-1539) Local fact-cache functionality
Title: Message Title Mike Smith updated an issue Puppet Task Runner / BOLT-1539 Local fact-cache functionality Change By: Mike Smith In various scenarios a user would have a potential target base of enough servers that they would need to arbitrarily filter them for running commands/scripts/tasks/plans. These facts could be used to either filter runs, inform logic, or provide data. An example of this in the Ansible feature set is fact-caching - [here is a blog|[https://jpmens.net/2015/01/29/caching-facts-in-ansible/]] that provides an end-to-end example. This feature was discussed in a Bolt workshop where the room was heavily Ansible users. In scenarios where PuppetDB is setup and accessible this would account for the above need. In various Puppet open source or enterprise deployments not all potential targets have Puppet agents nor do all users have access to PuppetDB. This was brought up during a Bolt workshop at Walmart with mostly Ansible users. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (BOLT-1539) Local fact-cache functionality
Title: Message Title Mike Smith updated an issue Puppet Task Runner / BOLT-1539 Local fact-cache functionality Change By: Mike Smith CS Priority: Needs Priority 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.348950.1583609276000.7649.1583781120029%40Atlassian.JIRA.
Jira (BOLT-1539) Local fact-cache functionality
Title: Message Title Mike Smith created an issue Puppet Task Runner / BOLT-1539 Local fact-cache functionality Issue Type: New Feature Assignee: Unassigned Created: 2020/03/07 11:27 AM Labels: bolt Priority: Normal Reporter: Mike Smith In various scenarios a user would have a potential target base of enough servers that they would need to arbitrarily filter them for running commands/scripts/tasks/plans. These facts could be used to either filter runs, inform logic, or provide data. An example of this in the Ansible feature set is fact-caching - [here is a blog|https://jpmens.net/2015/01/29/caching-facts-in-ansible/] that provides an end-to-end example. This feature was discussed in a Bolt workshop where the room was heavily Ansible users. In scenarios where PuppetDB is setup and accessible this would account for the above need. In various Puppet open source or enterprise deployments not all potential targets have Puppet agents nor do all users have access to PuppetDB. Add Comment
Jira (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Mike Smith commented on PUP-9337 Re: Puppet sets permissions for Puppet files every run Jesse Reynolds I was looking and was unsure if it should since it was resolved in a previous release of the agent software if I recall (like 6.0.7 vs 6.0.9 being packaged 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-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Mike Smith commented on PUP-9337 Re: Puppet sets permissions for Puppet files every run To restate when I was testing - deleting file and letting puppet recreate resolves issue (is a workaround) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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 Mike Smith updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Mike Smith Attachment: image-2018-12-03-14-15-00-161.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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 Mike Smith updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Mike Smith Attachment: image-2018-12-03-13-51-13-968.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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 Mike Smith updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Mike Smith Attachment: image-2018-12-03-13-50-41-861.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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 Mike Smith updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Mike Smith Attachment: image-2018-12-03-12-50-36-742.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9247) Puppet pidlock checks only look for PID if it is running, not process name
Title: Message Title Mike Smith updated an issue Puppet / PUP-9247 Puppet pidlock checks only look for PID if it is running, not process name Change By: Mike Smith Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9247) Puppet pidlock checks only look for PID if it is running, not process name
Title: Message Title Mike Smith updated an issue Puppet / PUP-9247 Puppet pidlock checks only look for PID if it is running, not process name Change By: Mike Smith Labels: agent linux puppet-agent 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 (PUP-9247) Puppet pidlock checks only look for PID if it is running, not process name
Title: Message Title Mike Smith updated an issue Puppet / PUP-9247 Puppet pidlock checks only look for PID if it is running, not process name Change By: Mike Smith *Puppet Version: 6.0.2 (or any)* *Puppet Server Version: 2018.1* *OS Name/Version: Windows (linux most likely as well)*When puppet runs it created the pidlock file with the pid of puppet. If puppet stops/crashes while running the lock file remains. Puppet reads the file, checks for pid as integer, and sees if that pid is running (system.kill(0) to see if alive). If ANY PID responds, it locks, even if the PID is not a puppet PID.*Desired Behavior: Puppet should check PID to see if it is running and its puppet, not just running.**Actual Behavior: if any process has that pid, puppet locks.*Steps to replicate (tested on windows 2016 with Puppet 6.0.2)1 - start puppet run with 'puppet agent -t'2 - while running stop the puppet/puppet-pxp agent services3 - open pidloclk file, there should be a PID there4 - change PID lock file contents to any other currently running PID5 - start puppet / run 'puppet agent -t' Affected Code: [https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/pidlock.rb#L55]This is the logic check that only determines if a pid is active, not who owns it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9247) Puppet pidlock checks only look for PID if it is running, not process name
Title: Message Title Mike Smith created an issue Puppet / PUP-9247 Puppet pidlock checks only look for PID if it is running, not process name Issue Type: Bug Affects Versions: PUP 6.0.2 Assignee: Unassigned Created: 2018/10/18 1:07 PM Priority: Normal Reporter: Mike Smith Puppet Version: 6.0.2 (or any) Puppet Server Version: 2018.1 OS Name/Version: Windows (linux most likely as well) When puppet runs it created the pidlock file with the pid of puppet. If puppet stops/crashes while running the lock file remains. Puppet reads the file, checks for pid as integer, and sees if that pid is running (system.kill(0) to see if alive). If ANY PID responds, it locks, even if the PID is not a puppet PID. Desired Behavior: Puppet should check PID to see if it is running and its puppet, not just running. Actual Behavior: if any process has that pid, puppet locks. Steps to replicate (tested on windows 2016 with Puppet 6.0.2) 1 - start puppet run with 'puppet agent -t' 2 - while running stop the puppet/puppet-pxp agent services 3 - open pidloclk file, there should be a PID there 4 - change PID lock file contents to any other currently running PID 5 - start puppet / run 'puppet agent -t' Add Comment
Jira (PUP-8732) Investigate if Puppet Device pluginsync can be limited to remote modules
Title: Message Title Mike Smith commented on PUP-8732 Re: Investigate if Puppet Device pluginsync can be limited to remote modules Testing now with SE demo env and first run is syncing all types and thus taking upwards of 15+ minutes. Appears to run ~2/sec with PE in Slice and the network testing 6509 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.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-6931) Scheduled_task only recognizes "xp" type tasks
Title: Message Title Mike Smith created an issue Puppet / PUP-6931 Scheduled_task only recognizes "xp" type tasks Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2016-11-17 at 12.33.48 PM.png Created: 2016/11/17 12:34 PM Priority: Normal Reporter: Mike Smith In testing an issue with mcollective scheduled tasks on a 2012r2 node, we noticed that the tasks are created as 2000/xp types. Changing a task to a newer type resulted in "puppet resource schedule_task" not finding the existing scheduled tasks. Add Comment
Jira (PUP-6660) cached catalogs setting not respected when --test is specified
Title: Message Title Mike Smith commented on PUP-6660 Re: cached catalogs setting not respected when --test is specified Ryan Coleman Looking at this from the user experience perspective, we have essentially told them (historically) "the default command line way to invoke a puppet run is puppet agent -t, and this will respect cached catalog settings." Pre 4.6.0 in cached catalog mode: Default command puppet agent -t Non-Default command puppet agent -t --no-use_cached_catalog Post 4.6.0 in cached catalog mode: Default command puppet agent -t --no-daemonize --onetime --verbose --no-usecacheonfailure --detailed-exitcodes --no-splay --show_diff
Jira (HI-518) make hiera_xxx functions delegate to lookup()
Title: Message Title
Mike Smith commented on HI-518
Re: make hiera_xxx functions delegate to lookup()
Brett Swift
I was working with Reid, and we tested these function overrides (Thanks Henrik Lindberg). You can place this in your site.pp (not a module) and it will override the hiera_XXX() functions to use lookup(). function hiera($key,$def = undef, $level = undef) {
function hiera($key,$def = undef, $level = undef) {
if $level != undef { fail('Lookup does not support hiera level override') }
lookup ($key,{'default_value' => $def})
}
function hiera_array($key,$def = undef, $level = undef) {
if $level != undef { fail('Lookup does not support hiera level override') }
lookup ($key,{'default_value' => $def, 'merge' => 'unique'})
}
