Jira (PDB-4266) Make package inventory actually sync
Title: Message Title Austin Blatt commented on PDB-4266 Re: Make package inventory actually sync Charlie Sharpsteen no, it missed the stop ship for 2018.1.9. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.295975.1550018788000.32225.1564113480308%40Atlassian.JIRA.
Jira (PUP-4647) Yum provider uses rpm -e to uninstall packages
Title: Message Title Trevor Vaughan commented on PUP-4647 Re: Yum provider uses rpm -e to uninstall packages Josh Cooper Looks like this may actually be a regression: https://tickets.puppetlabs.com/browse/PUP-1198 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.81272.1432290276000.32213.1564106880159%40Atlassian.JIRA.
Jira (PUP-9926) "Failed to apply catalog: undefined method `each' for #"
Title: Message Title Josh Cooper commented on PUP-9926 Re: "Failed to apply catalog: undefined method `each' for #" Passed CI in puppet-agent#1ba7e8ffe3b36e475d288a2aa3d31bfc668dbc93 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.318074.1564051611000.32166.1564101300451%40Atlassian.JIRA.
Jira (PUP-9926) "Failed to apply catalog: undefined method `each' for #"
Title: Message Title Nirupama Mantha commented on PUP-9926 Re: "Failed to apply catalog: undefined method `each' for #" Josh Cooper Gheorghe Popescu please update the ticket status Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.318074.1564051611000.32158.1564100520283%40Atlassian.JIRA.
Jira (PUP-9920) Prepare release announcement (Puppet Platform 6.7.1)
Title: Message Title Jean Bond commented on PUP-9920 Re: Prepare release announcement (Puppet Platform 6.7.1) Oh, sure, Nirupama Mantha, same URL as Tuesday: https://puppet.com/docs/puppet/6.7/release_notes_puppet.html I wouldn't say anything about burning the tag; that's doesn't explain anything and isn't really relevant to users. I did make a minor edit to my previous suggestion. Mostly users just need to know that we didn't release 6.7.1 and they aren't missing anything. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.318037.156401119.32098.1564099020678%40Atlassian.JIRA.
Jira (PUP-9909) Use file_sha256 to verify module tarballs
Title: Message Title Josh Cooper commented on PUP-9909 Re: Use file_sha256 to verify module tarballs Passed CI in 0c34993f87 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.317118.1563469306000.32031.1564097640406%40Atlassian.JIRA.
Jira (PUP-8587) Rich Data support (Binary and others) in Puppet 6.y
Title: Message Title Eric Thompson updated an issue Puppet / PUP-8587 Rich Data support (Binary and others) in Puppet 6.y Change By: Eric Thompson Team/s: Server Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.242634.1521740065000.32037.1564097880202%40Atlassian.JIRA.
Jira (PUP-9927) PKey.read monkey patch is incompatible with JRuby 9.1
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9927
PKey.read monkey patch is incompatible with JRuby 9.1
Change By:
Josh Cooper
Environment:
Puppetserver 6.0 uses JRuby 9.1 which is compatible (sort of) with MRI 2.3. However, that version of JRuby doesn't implement {{OpenSSL::PKey.read}} so our monkey patch in puppet fails:{noformat}$ ruby --versionjruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 Java HotSpot(TM) 64-Bit Server VM 25.162-b12 on 1.8.0_162-b12 +jit [darwin-x86_64]$ git rev-parse HEADf292c7ebcfd2b5e0f6696c40ae4f66ed7c053947$ bx rake parallel;specrake aborted!NameError: undefined method `read' for module `OpenSSL::PKey'/Users/josh/work/puppet/lib/puppet/util/monkey_patches.rb:104:in `'/Users/josh/work/puppet/lib/puppet/util/monkey_patches.rb:103:in `'/Users/josh/work/puppet/lib/puppet/util.rb:1:in `'/Users/josh/work/puppet/lib/puppet/util.rb:17:in `'/Users/josh/work/puppet/lib/puppet/util.rb:16:in `'...{noformat}
*Puppet Version Puppetserver 6.0 uses JRuby 9.1 which is compatible (sort of) with MRI 2.3. However, that version of JRuby doesn't implement \{{OpenSSL : **Puppet Server Version : **OS Name/Version:*Describe your issue PKey.read}} so our monkey patch in as much detail as possible…Describe steps to reproduce…*Desired Behavior puppet fails : * {noformat} *Actual Behavior:* $ ruby --version Please take a moment and attach any relevant log output and/or manifests jruby 9 . This will help us immensely when troubleshooting the issue 1 . Examples:Run puppet agent with 17.0 (2.3.3) 2018 - 04 - test 20 d8b1ff9 Java HotSpot(TM) 64 - Bit Server VM 25.162 - trace b12 on 1.8.0_162 - b12 +jit [darwin - debug x86_64] $ git rev-parse HEAD Relevant sections of {{ f292c7ebcfd2b5e0f6696c40ae4f66ed7c053947$ bx rake parallel;specrake aborted!NameError: undefined method `read' for module `OpenSSL::PKey' / var Users / log josh / puppetlabs work / puppetserver puppet / puppetserver lib/puppet/util/monkey_patches . log}} or any applicable logs from the same directory.For more detailed information turn up the server logs by upping the log level rb:104: in the server ` ' s logback.xml Relevant sections of configurations files ( /Users/josh/work/ puppet /lib/puppet/util/monkey_patches . conf, hiera.conf, Server rb:103:in ` ' s conf.d, defaults / sysconfig Users/josh/work/puppet/lib/puppet/util.rb:1:in ` ) >' /Users/josh/work/puppet/lib/puppet/util.rb:17:in `' For memory issues with server heap dumps are also helpful /Users/josh/work/puppet/lib/puppet/util . rb:16:in `' ...{noformat}
Jira (PUP-9920) Prepare release announcement (Puppet Platform 6.7.1)
Title: Message Title Nirupama Mantha commented on PUP-9920 Re: Prepare release announcement (Puppet Platform 6.7.1) Thanks Jean Bond , do we just say we had to burn the tag for 6.7.1? If you can add the link to the release note here, I will have the final version of the notes for Sara Meisburger updated in a comment 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318037.156401119.32011.1564096920107%40Atlassian.JIRA.
Jira (BOLT-126) Support WinRM with Kerberos (from Linux node)
Title: Message Title Ethan Brown commented on BOLT-126 Re: Support WinRM with Kerberos (from Linux node) We removed –realm switch in the PR in favor of using realm in the winrm definition. It's possible that we'll make it so that –user u...@domain.com will imply use of Kerberos. Windows should probably implicitly use the Kerberos ticket affiliated with the current logged on domain user ... making specification of realm unnecessary on Windows. It's also possible that realm will be changed to domain - that's still an open discussion. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.214093.150696560.31947.1564094940237%40Atlassian.JIRA.
Jira (PUP-9927) PKey.read monkey patch is incompatible with JRuby 9.1
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9927 PKey.read monkey patch is incompatible with JRuby 9.1 Change By: Josh Cooper Release Notes Summary: Puppet would fail to load under JRuby 9.1, which can occur if puppet-agent 6.4 or greater and puppetserver 6.0.x are installed on the same host. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318146.1564092258000.31930.1564094340065%40Atlassian.JIRA.
Jira (PUP-9927) PKey.read monkey patch is incompatible with JRuby 9.1
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9927 PKey.read monkey patch is incompatible with JRuby 9.1 Change By: Josh Cooper Fix Version/s: PUP 6.8.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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318146.1564092258000.31925.1564094100273%40Atlassian.JIRA.
Jira (PUP-9927) PKey.read monkey patch is incompatible with JRuby 9.1
Title: Message Title Josh Cooper created an issue Puppet / PUP-9927 PKey.read monkey patch is incompatible with JRuby 9.1 Issue Type: Bug Assignee: Unassigned Created: 2019/07/25 3:04 PM Environment: Puppetserver 6.0 uses JRuby 9.1 which is compatible (sort of) with MRI 2.3. However, that version of JRuby doesn't implement OpenSSL::PKey.read so our monkey patch in puppet fails: $ ruby --version jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 Java HotSpot(TM) 64-Bit Server VM 25.162-b12 on 1.8.0_162-b12 +jit [darwin-x86_64] $ git rev-parse HEAD f292c7ebcfd2b5e0f6696c40ae4f66ed7c053947 $ bx rake parallel;spec rake aborted! NameError: undefined method `read' for module `OpenSSL::PKey' /Users/josh/work/puppet/lib/puppet/util/monkey_patches.rb:104:in `'
Jira (PUP-9927) PKey.read monkey patch is incompatible with JRuby 9.1
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9927 PKey.read monkey patch is incompatible with JRuby 9.1 Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318146.1564092258000.31909.1564092300403%40Atlassian.JIRA.
Jira (PUP-9644) Improve documentation around sensitive data in puppet
Title: Message Title Jean Bond commented on PUP-9644 Re: Improve documentation around sensitive data in puppet Rob Braden, this ticket asks for documentation about what providers are supported, how data can be leaked, and corrections to inaccuracy about sensitive data behavior, but it doesn't provide information about those things. Can you recommend an SME for this ticket? (I know there's a related ticket, but it's 2+ years old and a whole lot to wade through and parse; if someone can offer more explicit answers, it would be really helpful.) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.304741.1555347266000.31903.1564092240139%40Atlassian.JIRA.
Jira (PUP-9513) Deprecate SSL host, validators, indirected types and termini
Title: Message Title Josh Cooper commented on PUP-9513 Re: Deprecate SSL host, validators, indirected types and termini Merged follow up to master in https://github.com/puppetlabs/puppet/commit/c60d6aaadb0311cc1232e91baa844642223c Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.297867.1551401113000.31870.1564090860520%40Atlassian.JIRA.
Jira (BOLT-126) Support WinRM with Kerberos (from Linux node)
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-126 Support WinRM with Kerberos (from Linux node) Change By: Chris Cowell Labels: DOCS docs docs_reviewed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.214093.150696560.31868.1564090860512%40Atlassian.JIRA.
Jira (PUP-8918) Finalize separation of CA from Ruby
Title: Message Title Josh Cooper commented on PUP-8918 Re: Finalize separation of CA from Ruby One gradual step might be to create a new ca directory outside of the existing ssl directory, and symlink from ssl/ca -> ca. This way rm -rf will unlink the symlink, but not follow it: [root@w4jl4a7y7wi0c0j puppet]# ln -s /etc/puppetlabs/puppet/ca /etc/puppetlabs/puppet/ssl/ca [root@w4jl4a7y7wi0c0j puppet]# chown puppet:puppet /etc/puppetlabs/puppet/ca [root@w4jl4a7y7wi0c0j puppet]# systemctl start puppetserver [root@w4jl4a7y7wi0c0j puppet]# /opt/puppetlabs/puppet/bin/puppet config set server `facter fqdn` --section main [root@w4jl4a7y7wi0c0j puppet]# /opt/puppetlabs/puppet/bin/puppet agent -t Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Caching catalog for w4jl4a7y7wi0c0j.delivery.puppetlabs.net Info: Applying configuration version '1564090147' Notice: Applied catalog in 0.02 seconds
Jira (PUP-9920) Prepare release announcement (Puppet Platform 6.7.1)
Title: Message Title Jean Bond commented on PUP-9920 Re: Prepare release announcement (Puppet Platform 6.7.1) Nirupama Mantha, the highlights for 6.7.2: This release fixes regression errors introduced in Puppet 6.7.0: When using the `mailalias` resource type, Puppet was unable to parse certain files and returned errors. When using the `puppetlabs-ciscopuppet` module, automatic relationships, such as autorequire, could cause the catalog application to fail. 6.7.1 was an unreleased version of Puppet. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318037.156401119.31721.1564086000118%40Atlassian.JIRA.
Jira (BOLT-1328) AWS inventory discovery integration
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-1328 AWS inventory discovery integration Change By: Chris Cowell Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.309594.1558455992000.31718.1564085940137%40Atlassian.JIRA.
Jira (PUP-9926) "Failed to apply catalog: undefined method `each' for #"
Title: Message Title Jean Bond updated an issue Puppet / PUP-9926 "Failed to apply catalog: undefined method `each' for #" Change By: Jean Bond Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.318074.1564051611000.31706.1564085700277%40Atlassian.JIRA.
Jira (BOLT-1447) Select a demo from available demos
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-1447 Select a demo from available demos Change By: Lucy Wyman Assignee: Tom Beech Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.314844.1562015098000.31691.1564084320166%40Atlassian.JIRA.
Jira (BOLT-1433) get_resources does not work with resource objects.
Title: Message Title Henrik Lindberg commented on BOLT-1433 Re: get_resources does not work with resource objects. If the concept of "resources" should exist while compiling in "script"/bolt mode then resource types should really also work, or it starts to be confusing. I can imagine that it starts to get tricky though since some operations on resources require that there is a Catalog - and there isn't one in "script mode". Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.314362.1561649732000.31683.1564083900136%40Atlassian.JIRA.
Jira (BOLT-1487) Make it easier for users to know and turn off analytics at install time
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-1487 Make it easier for users to know and turn off analytics at install time Issue Type: Improvement Assignee: Unassigned Created: 2019/07/25 12:21 PM Priority: Normal Reporter: Yasmin Rajabi Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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
Jira (BOLT-1207) Bolt should inform users when there is a new version available
Title: Message Title Tom Beech assigned an issue to Unassigned Puppet Task Runner / BOLT-1207 Bolt should inform users when there is a new version available Change By: Tom Beech Assignee: Tom Beech Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.301658.1553614758000.31657.1564081920227%40Atlassian.JIRA.
Jira (BOLT-1207) Bolt should inform users when there is a new version available
Title: Message Title Tom Beech assigned an issue to Tom Beech Puppet Task Runner / BOLT-1207 Bolt should inform users when there is a new version available Change By: Tom Beech Assignee: Tom Beech Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.301658.1553614758000.31612.1564080960541%40Atlassian.JIRA.
Jira (BOLT-1207) Bolt should inform users when there is a new version available
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1207 Bolt should inform users when there is a new version available Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.301658.1553614758000.31604.1564080900433%40Atlassian.JIRA.
Jira (BOLT-1384) Inventory command
Title: Message Title Corey Osman commented on BOLT-1384 Re: Inventory command This does satisfy my use case. Just tried this out. However, this creates a new problem in that the node count at the bottom will cause any script written against the output of the inventory command to break. The node count should be removed by default or added as a option. 192.168.70.104 192.168.70.110 192.168.70.119 192.168.70.125 192.168.70.128 192.168.70.135 192.168.70.136 55 targets Add Comment
Jira (PUP-9926) "Failed to apply catalog: undefined method `each' for #"
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9926 "Failed to apply catalog: undefined method `each' for #" Change By: Josh Cooper Release Notes Summary: Catalog application could fail failed when using a custom resource type whose autorelation method (autorequire, autobefore, etc) returned an instance of Puppet::Type instead of a resource name. Notably this occurred when using the ciscopuppet module: https://forge.puppet.com/puppetlabs/ciscopuppet Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.318074.1564051611000.31517.1564079520179%40Atlassian.JIRA.
Jira (PUP-9926) "Failed to apply catalog: undefined method `each' for #"
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9926 "Failed to apply catalog: undefined method `each' for #" Change By: Josh Cooper Release Notes Summary: Catalog application could fail when using a custom resource type whose autorelation method (autorequire, autobefore, etc) returned an instance of Puppet::Type instead of a resource name. Notably this occurred when using the ciscopuppet module: https://forge.puppet.com/puppetlabs/ciscopuppet 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318074.1564051611000.31505.1564079340237%40Atlassian.JIRA.
Jira (BOLT-1469) SPIKE: Support remote state for terraform inventory plugin
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1469 SPIKE: Support remote state for terraform inventory plugin Change By: Lucy Wyman Sprint: Bolt 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316121.1562857319000.31507.1564079340245%40Atlassian.JIRA.
Jira (BOLT-1469) SPIKE: Support remote state for terraform inventory plugin
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1469 SPIKE: Support remote state for terraform inventory plugin Change By: Lucy Wyman Summary: SPIKE: Support remote state for terraform inventory plugin Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.316121.1562857319000.31501.1564079280141%40Atlassian.JIRA.
Jira (BOLT-1449) Load Task based Plugins from the modulepath
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1449 Load Task based Plugins from the modulepath Change By: Lucy Wyman Sprint: Bolt 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314983.1562079167000.31487.1564079160409%40Atlassian.JIRA.
Jira (BOLT-1117) Powershell task helper library
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1117 Powershell task helper library Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295235.1549498793000.31481.1564078980691%40Atlassian.JIRA.
Jira (BOLT-1117) Powershell task helper library
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1117 Powershell task helper library Change By: Lucy Wyman Sprint: Bolt 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295235.1549498793000.31478.1564078980677%40Atlassian.JIRA.
Jira (BOLT-1434) Bolt demo commands should support tab completion
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1434 Bolt demo commands should support tab completion Change By: Lucy Wyman Sprint: Bolt 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314383.1561656097000.31465.1564078920196%40Atlassian.JIRA.
Jira (BOLT-1434) Bolt demo commands should support tab completion
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1434 Bolt demo commands should support tab completion Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314383.1561656097000.31466.1564078920220%40Atlassian.JIRA.
Jira (PDB-4388) Enable redhatfips-7-x86_64 test pipeline for puppetdb
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4388 Enable redhatfips-7-x86_64 test pipeline for puppetdb Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310005.1558650623000.31404.1564076220338%40Atlassian.JIRA.
Jira (PDB-4376) Test pe-puppetdb for redhatfips-7-x86_64
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4376 Test pe-puppetdb for redhatfips-7-x86_64 Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309991.1558650558000.31396.1564076160918%40Atlassian.JIRA.
Jira (BOLT-1384) Inventory command
Title: Message Title Tom Beech commented on BOLT-1384 Re: Inventory command A `bolt inventory show` command was added in 1.26.0 and supports human and json format. (https://puppet.com/docs/bolt/latest/bolt_new_features.html#section-fh3-j5c-j3b) Does this satisfy your use case? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.312167.1560296026000.31377.1564075980190%40Atlassian.JIRA.
Jira (PDB-4375) Build pe-puppetdb for redhatfips-7-x86_64
Title: Message Title Eric Thompson assigned an issue to Austin Blatt PuppetDB / PDB-4375 Build pe-puppetdb for redhatfips-7-x86_64 Change By: Eric Thompson Assignee: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309990.1558650553000.31360.1564075560255%40Atlassian.JIRA.
Jira (BOLT-1315) Collect analytics about Boltdir usage
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-1315 Collect analytics about Boltdir usage Change By: Chris Cowell Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.309059.1558038203000.31338.1564075380608%40Atlassian.JIRA.
Jira (PDB-4387) Enable redhatfips-7-x86_64 builds for puppetdb
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4387 Enable redhatfips-7-x86_64 builds for puppetdb Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310004.1558650619000.31323.1564075020706%40Atlassian.JIRA.
Jira (PUP-9926) "Failed to apply catalog: undefined method `each' for #"
Title: Message Title Josh Cooper commented on PUP-9926 Re: "Failed to apply catalog: undefined method `each' for #" Merged to 6.7.2_release in 6122a25869 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.318074.1564051611000.31287.1564074480164%40Atlassian.JIRA.
Jira (BOLT-1433) get_resources does not work with resource objects.
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1433 get_resources does not work with resource objects. Change By: Cas Donoghue Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314362.1561649732000.31263.1564073820183%40Atlassian.JIRA.
Jira (PUP-9914) v6.7.0 Breaks camptocamp-postfix
Title: Message Title Jean Bond updated an issue Puppet / PUP-9914 v6.7.0 Breaks camptocamp-postfix Change By: Jean Bond Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.317861.1563928891000.31249.1564073705818%40Atlassian.JIRA.
Jira (PUP-9563) Using max_queued_requests, agents return to originally scheduled run times
Title: Message Title Thomas Kishel commented on PUP-9563 Re: Using max_queued_requests, agents return to originally scheduled run times So ... would the puppet agent receiving the 503 need to send a signal to the puppet service to reset the timer in the following? https://github.com/puppetlabs/puppet/blob/5.5.x/lib/puppet/daemon.rb https://github.com/puppetlabs/puppet/blob/5.5.x/ext/windows/service/daemon.rb Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.299686.1552405921000.31241.1564073520475%40Atlassian.JIRA.
Jira (PDB-4460) Consider adding "extend lifetime" command alias
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4460 Consider adding "extend lifetime" command alias Issue Type: Improvement Assignee: Unassigned Created: 2019/07/25 9:48 AM Priority: Normal Reporter: Rob Browning Once we've finished the blockers, let's discuss the merit of an "extend lifetime" command alias, perhaps only initially supporting nodes. This would not be a new com,and, just an http-level alias/redirect to a suitable configure expiration command. The only real motivation would be to provide something for clients like the inventory service that's a bit less obtuse than (repeatedly) setting the expiration of a node to false as a way to extend its lifetime. Add Comment
Jira (PUP-9913) described_class.has_feature leaks global state
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9913 described_class.has_feature leaks global state Change By: Josh Cooper Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.317847.1563921337000.31194.1564073040051%40Atlassian.JIRA.
Jira (PDB-4459) Ensure sync handles node configure expiration correctly
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4459 Ensure sync handles node configure expiration correctly Issue Type: Improvement Assignee: Unassigned Created: 2019/07/25 9:39 AM Priority: Normal Reporter: Rob Browning I'd expect the considerations to be similar to those we encountered when adding configure expiration for facts. I think Zak may have had some specific ideas here. Imagine we may need some new test(s) and perhaps some adjustments to the sync process (not sure offhand yet). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4266) Make package inventory actually sync
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4266 Make package inventory actually sync Change By: Austin Blatt Fix Version/s: PDB 6.3.6 Fix Version/s: PDB 6.3.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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295975.1550018788000.31163.1564072260270%40Atlassian.JIRA.
Jira (PUP-9926) "Failed to apply catalog: undefined method `each' for #"
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9926 "Failed to apply catalog: undefined method `each' for #" Change By: Josh Cooper Fix Version/s: PUP 6.7.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.318074.1564051611000.31158.1564072200310%40Atlassian.JIRA.
Jira (PDB-4458) Adjust node expiration to accomodate the new node timestamp
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4458 Adjust node expiration to accomodate the new node timestamp Issue Type: Improvement Assignee: Unassigned Created: 2019/07/25 9:27 AM Priority: Normal Reporter: Rob Browning Adjust the gc/node-expiration to handle the new node expiration setting and timestamp (PDB-4342) in the same way we handle facts, i.e. when expiration is set to false, never expire, when true, consider the modification timestamp as another relevant timestamp when computing the overall expiration time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4342) Add basis for making node lifetimes configurable
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-4342
Add basis for making node lifetimes configurable
Change By:
Rob Browning
Make nodes lifetimes configurable like factset's are. When expiration is set to false, the node should not be expired, even if it otherwise would have been, i.e. even if all of its reports, catalog, factset, etc. are gone. Add a node "timestamp" and boolean (perhaps in the certnames table) that will behave like the other lifetime-related timestamps, i.e. the factsets/reports timestamps, and adjust the configure expiration command to affect it the two values when the "expires" field includes "node"., i.e. {"certname": ... "expire": {"node": } ...}. (Not sure yet whether configure expiration should initially allow more than one field in expires, i.e. "facts" and "node" -- not critical for now.). The configure expiration command should behave like it does for facts, maybe reactivating the node, etc. (If the boolean ends up in the certnames table, not sure what to call it -- "expire" and "expire_updated" would more or less match facts, and be accurate, but might be confusing? Given the existing "expired" column.) This ticket only needs to cover the schema/migration, command adjustment, and attendant docs (e.g. the configure expiration wire format, and possibly information about the new node timestamp). Related tickets will cover the remaining work.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4266) Make package inventory actually sync
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4266 Make package inventory actually sync Change By: Austin Blatt Fix Version/s: PDB 6.3.6 Fix Version/s: PDB 6.0.5 Fix Version/s: PDB 5.2.10 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295975.1550018788000.31135.1564071900653%40Atlassian.JIRA.
Jira (PDB-4342) Add basis for making node lifetimes configurable
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4342 Add basis for making node lifetimes configurable Change By: Rob Browning Summary: Add a basis for making node lifetime timestamp, affected by configure expiration lifetimes configurable Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.304555.1555024076000.31107.1564071600454%40Atlassian.JIRA.
Jira (PDB-4342) Add a node lifetime timestamp, affected by configure expiration
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-4342
Add a node lifetime timestamp, affected by configure expiration
Change By:
Rob Browning
Add a node "timestamp" (perhaps in the certnames table) that will behave like the other lifetime-related timestamps, i.e. the factsets/reports timestamps, and adjust the configure expiration command to affect it when the "expires" field includes "node". , i.e. {"certname": ... "expire": {"node": } ...}. (Not sure yet whether configure expiration should initially allow more than one field in expires, i.e. "facts" and "node" -- not critical for now.) . The configure expiration command should behave like it does for facts, maybe reactivating the node, etc. This ticket only needs to cover the schema/migration, command adjustment, and attendant docs (e.g. the configure expiration wire format, and possibly information about the new node timestamp). Related tickets will cover the remaining work.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4342) Add a node lifetime timestamp, affected by configure expiration
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4342 Add a node lifetime timestamp, affected by configure expiration Change By: Rob Browning Add a node "timestamp" (perhaps in the certnames table) that will behave like the other lifetime-related timestamps, i.e. the factsets/reports timestamps, and adjust the configure expiration command to affect it when the "expires" field includes "node". (Not sure yet whether configure expiration should initially allow more than one field in expires, i.e. "facts" and "node" -- not critical for now.)This ticket only needs to cover the schema/migration and , command adjustment , and attendant docs (e . g. the configure expiration wire format, and possibly information about the new node timestamp). Related tickets will cover the remaining 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
Jira (PDB-4342) Add a node lifetime timestamp, affected by configure expiration
Title: Message Title Rob Browning commented on PDB-4342 Re: Add a node lifetime timestamp, affected by configure expiration Also adjusting the epic (and it's tickets) to reflect the amended plan. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.304555.1555024076000.31049.1564070880339%40Atlassian.JIRA.
Jira (PDB-4342) Add a node lifetime timestamp, affected by configure expiration
Title: Message Title Rob Browning commented on PDB-4342 Re: Add a node lifetime timestamp, affected by configure expiration Excellent point. After discussion, a good bit of it with Zak while working on the other configure expiration related work, adding a real node timestamp seems like the best way forward, so I've adjusted the ticket accordingly. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.304555.1555024076000.31036.1564070820556%40Atlassian.JIRA.
Jira (PDB-4342) Add a node lifetime timestamp, affected by configure expiration
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-4342
Add a node lifetime timestamp, affected by configure expiration
Change By:
Rob Browning
Add a node "timestamp" (perhaps in the certnames table) that behaves will behave like the other lifetime-related timestamps, i.e. the factsets/reports timestamps Extend , and adjust the configure expiration command to allow affect it when the " node expires " as a value in the field includes " expire node " . (Not sure yet whether configure expiration should initially allow more than one field in expires , i.e. { " node facts " : ...} and have the command behave as it does for facts, but Support a way for users to explicitly refresh the timestamp used for " node TTL.This can be accomplished currently by repeatedly sending *configure expiration* commands " -- not critical for a node with *expire now . facts = true* (see linked ticket for more detail ) We should make this more explicit (maybe adding a new command) This ticket only needs to cover the schema/migration and look into command adjustment. Related tickets will cover the possibility of allowing bulk updates given a list of certnames remaining work .
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4342) Add a node lifetime timestamp, affected by configure expiration
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4342 Add a node lifetime timestamp, affected by configure expiration Change By: Rob Browning Summary: Add a node lifetime " timestamp " , affected by configure expiration Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.304555.1555024076000.31014.1564070413139%40Atlassian.JIRA.
Jira (PDB-4342) Add a node lifetime "timestamp"
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-4342
Add a node lifetime "timestamp"
Change By:
Rob Browning
Add a node "timestamp" (perhaps in the certnames table) that behaves like the other lifetime-related timestamps, i.e. the factsets/reports timestamps Extend the configure expiration command to allow "node" as a value in the "expire" field, i.e. {"node": ...} and have the command behave as it does for facts, but Support a way for users to explicitly refresh the timestamp used for node TTL.This can be accomplished currently by repeatedly sending *configure expiration* commands for a node with *expire.facts = true* (see linked ticket for more detail)We should make this more explicit (maybe adding a new command) and look into the possibility of allowing bulk updates given a list of certnames.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from
Jira (PDB-4342) Add a node lifetime "timestamp"
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4342 Add a node lifetime "timestamp" Change By: Rob Browning Summary: Add a node lifetime " timestamp and connect to configure expiration " Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.304555.1555024076000.30989.1564070160810%40Atlassian.JIRA.
Jira (PDB-4342) Add a node timestamp and connect to configure expiration
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-4342
Add a node timestamp and connect to configure expiration
Change By:
Rob Browning
Extend the configure expiration command to allow "node" as a value in the "expire" field, i.e. {"node": ...} and have the command behave as it does for facts, butSupport a way for users to explicitly refresh the timestamp used for node TTL.This can be accomplished currently by repeatedly sending *configure expiration* commands for a node with *expire.facts = true* (see linked ticket for more detail)We should make this more explicit (maybe adding a new command) and look into the possibility of allowing bulk updates given a list of certnames.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "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
Jira (PDB-4342) Add a node timestamp and connect to configure expiration
Title: Message Title
Rob Browning updated an issue
PuppetDB / PDB-4342
Add a node timestamp and connect to configure expiration
Change By:
Rob Browning
Extend the configure expiration command to allow "node" as a value in the "expire" field, i.e. {"node": ...} Support a way for users to explicitly refresh the timestamp used for node TTL.This can be accomplished currently by repeatedly sending *configure expiration* commands for a node with *expire.facts = true* (see linked ticket for more detail)We should make this more explicit (maybe adding a new command) and look into the possibility of allowing bulk updates given a list of certnames.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "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
Jira (PDB-4342) Add a node timestamp and connect to configure expiration
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4342 Add a node timestamp and connect to configure expiration Change By: Rob Browning Summary: Support an option to update the Add a node timestamp used and connect to expire nodes configure expiration Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.304555.1555024076000.30965.1564069920682%40Atlassian.JIRA.
Jira (PDB-4323) Update explicit lifetime node behavior in PDB
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4323 Update explicit lifetime node behavior in PDB Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.302291.1553880231000.30930.1564069740621%40Atlassian.JIRA.
Jira (PDB-4323) Update explicit lifetime node behavior in PDB
Title: Message Title Rob Browning assigned an issue to Unassigned PuppetDB / PDB-4323 Update explicit lifetime node behavior in PDB Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.302291.1553880231000.30935.1564069740659%40Atlassian.JIRA.
Jira (PDB-4373) PDB has issues upgrading to versions later than 6.1 on centos6
Title: Message Title Rob Browning commented on PDB-4373 Re: PDB has issues upgrading to versions later than 6.1 on centos6 The related ezbake pr has been merged https://github.com/puppetlabs/ezbake/pull/541 and so now we need to get back to finishing up and testing https://github.com/puppetlabs/puppetdb/pull/3017 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.309068.155804266.30901.1564068720362%40Atlassian.JIRA.
Jira (PDB-4457) Installing PDB with module on Redhat 7 in FIPS mode fails
Title: Message Title
Maggie Dreyer created an issue
PuppetDB / PDB-4457
Installing PDB with module on Redhat 7 in FIPS mode fails
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/07/25 8:26 AM
Priority:
Normal
Reporter:
Maggie Dreyer
When installing PuppetDB with the puppetdb module on Redhat 7 in FIPS mode, the following error reliably occurs:
Info: Applying configuration version '1564068144'
Notice: /Stage[main]/Postgresql::Repo::Yum_postgresql_org/File[/etc/pki/rpm-gpg/RPM-GPG-KEY-PGDG-96]/ensure: defined content as '{sha256}5c7bdbdfa666de461e14007f7207d4d4f8c0565c56a88bb24c77f25b856203d4'
Error: Could not prefetch yumrepo provider 'inifile': Section "pl-puppet-agent-641a430f5eff10b87df36d3bbbf3d17db4f206be" is already defined, cannot redefine (file: /etc/yum.repos.d/pl-puppet-agent-641a430f5eff10b87df36d3bbbf3d17db4f206be-redhatfips-7-x86_64.repo)
Error: Failed to apply catalog: Section "pl-puppet-agent-641a430f5eff10b87df36d3bbbf3d17db4f206be" is already defined, cannot redefine (file: /etc/yum.repos.d/pl-puppet-agent-641a430f5eff10b87df36d3bbbf3d17db4f206be-redhatfips-7-x86_64.repo)
Jira (BOLT-1410) Add plugin analytics
Title: Message Title Chris Cowell updated an issue Puppet Task Runner / BOLT-1410 Add plugin analytics Change By: Chris Cowell Labels: docs docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.313047.1560895161000.30860.1564067460428%40Atlassian.JIRA.
Jira (FACT-1944) Investigate custom facts
Title: Message Title Oana Tanasoiu assigned an issue to Unassigned Facter / FACT-1944 Investigate custom facts Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.316808.1563365164000.30780.1564062300343%40Atlassian.JIRA.
Jira (FACT-1944) Investigate custom facts
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-1944 Investigate custom facts Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.316808.1563365164000.30751.1564061640252%40Atlassian.JIRA.
Jira (PUP-9914) v6.7.0 Breaks camptocamp-postfix
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9914 v6.7.0 Breaks camptocamp-postfix Change By: Gheorghe Popescu Sprint: NW - 2019-08-07 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.317861.1563928891000.30720.1564060501050%40Atlassian.JIRA.
Jira (PUP-9914) v6.7.0 Breaks camptocamp-postfix
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-9914 v6.7.0 Breaks camptocamp-postfix Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.317861.1563928891000.30683.1564060440826%40Atlassian.JIRA.
Jira (PUP-9914) v6.7.0 Breaks camptocamp-postfix
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9914 v6.7.0 Breaks camptocamp-postfix Change By: Gheorghe Popescu Team: Night's Watch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.317861.1563928891000.30707.1564060500977%40Atlassian.JIRA.
Jira (PUP-9926) "Failed to apply catalog: undefined method `each' for #"
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9926 "Failed to apply catalog: undefined method `each' for #" Change By: Gheorghe Popescu Sprint: NW - 2019-08-07 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.318074.1564051611000.30681.1564060440816%40Atlassian.JIRA.
Jira (PUP-9926) "Failed to apply catalog: undefined method `each' for #"
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9926 "Failed to apply catalog: undefined method `each' for #" Change By: Gheorghe Popescu Team: Night's Watch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.318074.1564051611000.30679.1564060440798%40Atlassian.JIRA.
Jira (PUP-9926) "Failed to apply catalog: undefined method `each' for #"
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-9926 "Failed to apply catalog: undefined method `each' for #" Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.318074.1564051611000.30675.1564060380243%40Atlassian.JIRA.
Jira (PUP-9915) Debian: avoid updating systemd defaults for every release
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-9915 Debian: avoid updating systemd defaults for every release Change By: Gabriel Nagy Team: Night's Watch Sprint: NW - 2019-08-07 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.317870.1563960604000.30645.1564057020202%40Atlassian.JIRA.
Jira (PUP-9926) "Failed to apply catalog: undefined method `each' for #"
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-9926
"Failed to apply catalog: undefined method `each' for #"
Change By:
David Schmitt
*Puppet Version:* 6.7.0*Puppet Server Version:* n/a*OS Name/Version:* n/aThe ciscopuppet acceptance tests fail on trivial catalogs with "Error: Failed to apply catalog: undefined method `each' for #", due to https://github.com/puppetlabs/puppet/commit/6c257fc7827989c2af2901f974666f0f23611153#diff-7f00f7dbc0f9bfecbaadfec966d0b8b1L2149 . Specifically, the change from {{[list]}} to {{Array(list)}} in the chunk linked.Observe the following pry example to show the issue:{code}[10] pry(main)> class Foo[10] pry(main)* include Enumerable[10] pry(main)* end => Foo[11] pry(main)> Foo.new.to_aNoMethodError: undefined method `each' for #from (pry):13:in `to_a'[12] pry(main)> Array(Foo.new)NoMethodError: undefined method `each' for #from (pry):14:in `to_a'[13] pry(main)> [Foo.new]=> [#][14] pry(main)> class Foo2[14] pry(main)* end => nil[15] pry(main)> Array(Foo2.new)=> [#][16] pry(main)> {code}This can be traced back to https://github.com/puppetlabs/puppet/blob/0c34993f87f100f3bbbccfbb5b000a51094fce5e/lib/puppet/type.rb#L2276 without having a `each` method. This bug was introduced in 2005 (see my previous unrelated analysis of this in https://twitter.com/dev_el_ops/status/1141814653653311489?s=19).*Desired Behavior:*Puppet not failing on a ruby error.*Actual Behavior:*Puppet failing on a ruby error. Full stacktrace from https://jenkins-master-prod-1.delivery.puppetlabs.net/view/modules/view/networking/view/ciscopuppet/job/forge-netdev_cisco-ciscopuppet_intn-sys_smoke-develop/lastFailedBuild/PLATFORM=cisconx-64default.%257Bssh%253D%257Buser%253Dadmin%252Cpassword%253Dadmin%257D%257D,WORKER_LABEL=beaker/consoleFull : {code}00:06:07.170 * TestStep :: 1.1 Apply default manifest with 'default' as a string in attributes [ensure => present] :: MANIFEST00:06:07.170 test_manifest :: manifest:00:06:07.171 000:06:07.171 test_manifest :: check puppet apply cmd (code: [0, 2])00:06:07.171 00:06:16.260 cisco_tacacs_server { 'default': ensure => present }00:06:16.260 00:06:16.260 cisco_aaa_authorization_login_cfg_svc { 'default':00:06:16.260 00:06:16.260 ensure => 'present',00:06:16.260 groups => 'default',00:06:16.260 method => 'default',00:06:16.260 00:06:16.260 }00:06:16.260 Notice: Compiled catalog for sut in environment production in 0.12 seconds00:06:16.271 Info: Applying configuration version '1564016874'00:06:16.271 Error: Failed to apply catalog: undefined method `each' for #00:06:16.271 /tmp/jenkins/workspace/forge-netdev_cisco-ciscopuppet_intn-sys_smoke-develop/PLATFORM/cisconx-64default.%7Bssh%3D%7Buser%3Dadmin%2Cpassword%3Dadmin%7D%7D/WORKER_LABEL/beaker/.bundle/gems/gems/puppet-6.7.0/lib/puppet/type.rb:2190:in `to_a'00:06:16.271
Jira (PUP-9914) v6.7.0 Breaks camptocamp-postfix
Title: Message Title Vadym Chepkov commented on PUP-9914 Re: v6.7.0 Breaks camptocamp-postfix I don't think the issue is specific to postfix module. Anyone using mailalias resource type is affected. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.317861.1563928891000.30512.1564047720303%40Atlassian.JIRA.
Jira (PUP-9814) pxp-agent.conf file missing Administrators rights when puppet agent run as SYSTEM
Title: Message Title John O'Connor commented on PUP-9814 Re: pxp-agent.conf file missing Administrators rights when puppet agent run as SYSTEM Thanks Gabriel Nagy - I'm thinking there are two ways we could tackle this one: Modify the modify to explicitly set the Group to Administrators (my preference) Intercept the file: type and ensure any files under ProgramData\PuppetLabs or a sub-directory of that have group set as Administrators (quite a hacky approach hence my preference for the other). /cc Gheorghe Popescu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.315397.1562338786000.30504.1564046580141%40Atlassian.JIRA.
Jira (FACT-1962) Create list of global/nested facts
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-1962 Create list of global/nested facts Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.317074.1563449204000.30495.1564042140089%40Atlassian.JIRA.
Jira (FACT-1965) Create Gemfile and Travis for benchmark tool
Title: Message Title Oana Tanasoiu assigned an issue to Unassigned Facter / FACT-1965 Create Gemfile and Travis for benchmark tool Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.318067.1564041936000.30491.1564042020197%40Atlassian.JIRA.
Jira (FACT-1965) Create Gemfile and Travis for benchmark tool
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-1965 Create Gemfile and Travis for benchmark tool Issue Type: Task Assignee: Oana Tanasoiu Created: 2019/07/25 1:05 AM Priority: Normal Reporter: Oana Tanasoiu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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
Jira (PUP-9814) pxp-agent.conf file missing Administrators rights when puppet agent run as SYSTEM
Title: Message Title Gabriel Nagy commented on PUP-9814 Re: pxp-agent.conf file missing Administrators rights when puppet agent run as SYSTEM Looks like pxp-agent.conf comes from here: https://github.com/puppetlabs/puppet-enterprise-modules/blob/irving/modules/puppet_enterprise/manifests/pxp_agent.pp#L105 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.315397.1562338786000.30460.1564040640307%40Atlassian.JIRA.
