Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Geoff Nichols commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo Nick Lewis, Alex Dreyer, Rob Braden, Molly Waggett - beyond Garrett's recommended documentation update, what are your thoughts on next actions? /cc Kami Olszewski Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.308071.1557427938000.13435.1562891400286%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1454) Bolt is super slow
Title: Message Title Nick Lewis commented on BOLT-1454 Re: Bolt is super slow I filed a PR against net-ssh with some improvements to known_hosts parsing. There's more work to be done to only parse it once, but this is a substantial improvement anyway. https://github.com/net-ssh/net-ssh/pull/682 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.315226.1562163484000.13408.1562889900200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1328) AWS inventory discovery integration
Title: Message Title Tom Beech updated an issue Puppet Task Runner / BOLT-1328 AWS inventory discovery integration Change By: Tom Beech Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309594.1558455992000.13384.1562888520295%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1444) Command validation regex should ensure attendees follow 'script'
Title: Message Title Tom Beech assigned an issue to Tom Beech Puppet Task Runner / BOLT-1444 Command validation regex should ensure attendees follow 'script' 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 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.314806.156201450.13295.1562887800229%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9821) User Password Debug Tests
Title: Message Title Kris Bosland created an issue Puppet / PUP-9821 User Password Debug Tests Issue Type: Improvement Assignee: Unassigned Created: 2019/07/11 4:26 PM Priority: Normal Reporter: Kris Bosland Unit tests should check that passwords are not wriiten to debug logs for user providers Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1454) Bolt is super slow
Title: Message Title Nick Lewis commented on BOLT-1454 Re: Bolt is super slow I've found a couple things. The first is that net-ssh's parsing of known_hosts is inherently quite slow (~300ms with 20k lines). The other is that net-ssh parses the known_hosts file once for every host being targeted. The first issue is relatively easy to fix, but the latter requires a bigger restructure. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.315226.1562163484000.13215.1562885220158%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9754) Log resident configuration upon daemon launch
Title: Message Title
Garrett Guillotte updated an issue
Puppet / PUP-9754
Log resident configuration upon daemon launch
Change By:
Garrett Guillotte
*Problem Statement*When attempting to diagnose issues with configuration drift within Puppet agent itself (such as changes to `puppet.conf` not picked up by the agent), there is no way to confirm that the resident configuration is the same as the current state of the configuration files.For example, we can confirm configuration file settings with {{puppet config print}} and lookup PE keys with {{puppet lookup}}, but these only reflect what's currently written to the filesystem—if the daemon launched with different settings, there's no equivalent command to confirm its resident configuration.*Suggested Improvement*Either at info or debug logging levels, dump the configuration used by the daemon on launch and also when the daemon reloads the configuration. *Use cases** User Dougie wants to change a setting on disk (for instance, in {{puppet.conf}} or in PE Hiera keys) that doesn't have an obvious measurable impact, but he still wants to confirm that the change is picked up by the daemon after it is restarted. (For instance, Dougie might want to confirm that changing a setting in {{puppet.conf}} takes effect if the setting also exists in Hiera or the classifier.) If the daemon dumps its settings on launch with debug-level logging enabled, Dougie could confirm that the daemon's new settings match the settings on disk.* User Dougie launches the agent daemon, then user Bob changes the agent settings on disk. The agent daemon then runs uninterrupted for a length of time. Dougie is concerned that the setting on disk might have been changed, and if so wants to revert the change. However, he cannot remember the altered setting's original value. If the daemon dumped its settings on launch at info log level, Dougie could confirm that the settings on disk were changed and revert them to their original value.* User Dougie launches the agent daemon, then user Bob changes the agent settings on disk. The agent daemon then runs uninterrupted for a length of time. The agent eventually exhibits signs of a potential issue related to an agent setting, and Dougie calls Support. Using the settings that Bob set on disk, Support cannot reproduce the problem. It also does not appear that the daemon reloaded the settings from disk. Dougie does not remember how the settings Bob changed were configured when the running daemon was launched. If the daemon dumped its settings on launch at info log level, Support could confirm the settings in use by the daemon and attempt to reproduce the issue.
Jira (PDB-4449) Upgrade to lein 2.9.1+
Title: Message Title Rob Browning moved an issue PuppetDB / PDB-4449 Upgrade to lein 2.9.1+ Change By: Rob Browning Scrum Team: PuppetDB Key: CT PDB - 69 4449 Project: PE Client Tools PuppetDB Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.316188.1562883332000.13131.1562883420425%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1454) Bolt is super slow
Title: Message Title Nick Lewis commented on BOLT-1454 Re: Bolt is super slow It's also only using one core on my machine. That's a limitation of Ruby, unfortunately. But it doesn't seem to be a computationally intensive task in my case, since it's still running very quickly. I found a potentially related issue: https://github.com/net-ssh/net-ssh/issues/567 If I cat my known_hosts file into itself a few times, Bolt takes more than twice as long to run. Does the host you're running from have a particularly large known_hosts file? Weirdly, this seems to even be the case if I run with --no-host-key-check set... Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.315226.1562163484000.13059.1562882580098%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1933) Include more chassis IDs in facter
Title: Message Title Jarret Lavallee updated an issue Facter / FACT-1933 Include more chassis IDs in facter Change By: Jarret Lavallee CS Priority: Needs Priority 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 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.314629.1561725724000.12857.1562875080438%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1936) facter -p segfaults with facts that call open-uri.open
Title: Message Title
Thomas Kishel updated an issue
Facter / FACT-1936
facter -p segfaults with facts that call open-uri.open
Change By:
Thomas Kishel
*Puppet Version:* 6.0.9*Facter Version:* 3.12.4 (commit ce9452fd2d15ed91eed9b8cc7823af783c9275a8) *OS Name/Version:* Windows 2012This custom fact succeeds on Linux but segfaults on Windows ... but only when calling {{facter -p}} not with {{puppet facts}} or {{puppet agent -t}} {code}require 'open-uri'require 'json'require 'timeout'Facter.add('test') do response = nil beginurl = ''Timeout::timeout(4) do response = open(url).readend rescuenil end if !response.to_s.empty?result = JSON.parse(response)setcode do result['ip']end endend{code} {code}C:\Users\Administrator>facter -p C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/net/protocol.rb:45: [BUG] Segmentation fault ruby 2.5.3p105 ( 2018-10-18 revision 65156) [x64-mingw32] -- Control frame information --- c:0082 p: s:0522 e:000521 CFUNC :wait_readable c:0081 p:0093 s:0517 e:000516 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/net/protocol.rb:45 c:0080 p:0557 s:0510 E:002178 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/net/http.rb:981 c:0079 p:0004 s:0497 e:000496 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/net/http.rb:920 c:0078 p:0029 s:0493 e:000492 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/net/http.rb:909 c:0077 p:0521 s:0489 e:000488 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/open-uri.rb:337 c:0076 p:0017 s:0468 e:000467 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/open-uri.rb:755 c:0075 p:0029 s:0461 e:000460 BLOCK C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/open-uri.rb:226 [FINISH] c:0074 p: s:0458 e:000457 CFUNC :catch c:0073 p:0365 s:0453 E:001398 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/open-uri.rb:224 c:0072 p:0328 s:0438 e:000437 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/open-uri.rb:165 c:0071 p:0018 s:0426 e:000425 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/open-uri.rb:735 c:0070 p:0071 s:0420 e:000419 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/open-uri.rb:35 c:0069 p:0007 s:0412 e:000411 BLOCK C:/ProgramData/PuppetLabs/puppet/cache/lib/facter/test.rb:11 c:0068 p:0030 s:0409 E:002298 BLOCK C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/timeout.rb:93 c:0067 p:0005 s:0403 e:000402 BLOCK C:/Program Files/Puppet
Jira (FACT-1936) facter -p segfaults with facts that call open-uri.open
Title: Message Title Thomas Kishel updated an issue Facter / FACT-1936 facter -p segfaults with facts that call open-uri.open Change By: Thomas Kishel Attachment: seg.txt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.316163.1562873035000.12820.1562873460148%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1936) facter -p segfaults with facts that call open-uri.open
Title: Message Title
Thomas Kishel created an issue
Facter / FACT-1936
facter -p segfaults with facts that call open-uri.open
Issue Type:
Bug
Assignee:
Unassigned
Components:
Windows
Created:
2019/07/11 12:23 PM
Priority:
Normal
Reporter:
Thomas Kishel
Puppet Version: 6.0.9 Facter Version: 3.12.4 (commit ce9452fd2d15ed91eed9b8cc7823af783c9275a8) OS Name/Version: Windows 2012 This custom fact succeeds on Linux but segfaults on Windows ... but only when calling facter -p not with puppet facts or puppet agent -t
require 'open-uri'
require 'json'
require 'timeout'
Facter.add('test') do
Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title Kevin Reeuwijk commented on BOLT-1466 Re: Inventory configuration precedence is confusing Can you force override the transport by specifying '--transport pcp' as 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315922.1562780625000.12761.1562871420152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9820) managing a File user or group or mode breaks require on Windows
Title: Message Title Thomas Kishel commented on PUP-9820 Re: managing a File user or group or mode breaks require on Windows Caused by a call to validate here: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/file/windows.rb#L85 Which calls supports_acl? which includes the "Failed to get volume information" error here: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/security.rb#L163 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.316149.1562868793000.12645.1562869200198%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9820) managing a File user or group or mode breaks require on Windows
Title: Message Title
Thomas Kishel created an issue
Puppet / PUP-9820
managing a File user or group or mode breaks require on Windows
Issue Type:
Bug
Assignee:
Unassigned
Components:
Windows
Created:
2019/07/11 11:13 AM
Priority:
Normal
Reporter:
Thomas Kishel
Puppet Version:* 6.0.9
Puppet Server Version: 2019.0.3
OS Name/Version: Windows 2002
A File resource that depends (via require) on another resource to create the volume of the file fails to honor the dependency when managing owner, group, and/or mode ... but only on Windows where it generates a Validation ... failed error.
node 'pe-201903-agent-win2012' {
exec { 'Make Drive':
command => 'sleep 5',
provider => powershell,
Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title Lucy Wyman commented on BOLT-1466 Re: Inventory configuration precedence is confusing Making targets in the inventory context aware of how they are being invoked isn't feasible. When invoking a single group it's easy to know what context should take precedence - that of the group being invoked. But what if I invoke multiple groups that a node is a part of? Which group config should take precedence? What if I invoke the node by name, and it's a member of multiple groups? The inventory is fundamentally a way of storing connection information about targets. Groups are just ways of short-handing a list of those targets and providing some precedence to config options, but they don't (and, as far in the future as I can see, won't) provide the context for those targets to be run in during a particular Bolt invocation. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.315922.1562780625000.12550.1562867220272%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9819) Puppet Failure on MacOS 10.15 'Catalina' Beta3
Title: Message Title Josh Cooper commented on PUP-9819 Re: Puppet Failure on MacOS 10.15 'Catalina' Beta3 Thanks for the report. FWIW, I don't think Catalina is a supported OSX platform yet, but is planned to be. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.316143.1562866804000.12532.1562866980321%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9819) Puppet Failure on MacOS 10.15 'Catalina' Beta3
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9819 Puppet Failure on MacOS 10.15 'Catalina' Beta3 Change By: Josh Cooper Team: Puppet Romania Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316143.1562866804000.12536.1562866980336%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9819) Puppet Failure on MacOS 10.15 'Catalina' Beta3
Title: Message Title
Marshall Taylor updated an issue
Puppet / PUP-9819
Puppet Failure on MacOS 10.15 'Catalina' Beta3
Change By:
Marshall Taylor
Summary:
{brief summary of issue} Puppet Failure on MacOS 10.15 'Catalina' Beta3
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "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.316143.1562866804000.12525.1562866920187%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9819) {brief summary of issue}
Title: Message Title
Marshall Taylor created an issue
Puppet / PUP-9819
{brief summary of issue}
Issue Type:
Bug
Affects Versions:
PUP 6.4.0
Assignee:
Unassigned
Components:
Catalog Application
Created:
2019/07/11 10:40 AM
Environment:
We have a mix of ~50 10.[13,14].x MacOS laptops using a Ubuntu 18.04.2 LTS system for our master. Both agents and server are running 6.4.0.
Fix Versions:
PUP 6.4.0
Priority:
Normal
Reporter:
Marshall Taylor
Puppet Version: 6.4.0 Puppet Server Version: 6.4.0 OS Name/Version: MacOS 10.15 Catalina Beta3 Running 'puppet agent --test' outputs:
mtaylor@Marshalls-Air ~ % sudo /opt/puppetlabs/bin/puppet agent --test
Password:
Jira (BOLT-1339) Build pe-bolt-server for redhatfips-7-x86_64
Title: Message Title Jonathan Morris updated an issue Puppet Task Runner / BOLT-1339 Build pe-bolt-server for redhatfips-7-x86_64 Change By: Jonathan Morris 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309966.155865044.12419.1562865240277%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9818) PAL fixes to support AST compilation
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9818 PAL fixes to support AST compilation Change By: Maggie Dreyer 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315708.1562697889000.12403.1562864880059%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1457) Bolt 1.26.0 2019-07-09 Release
Title: Message Title Tom Beech updated an issue Puppet Task Runner / BOLT-1457 Bolt 1.26.0 2019-07-09 Release Change By: Tom Beech 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 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.315749.156270623.12381.1562864461167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1470) Plugin parameters can't use other plugins to get data
Title: Message Title Nick Maludy commented on BOLT-1470 Re: Plugin parameters can't use other plugins to get data Here's an example inventory file for using a task plugin to retrieve config data and/or inventory. The task i'm calling out to for config data accesses HashiCorp Vault and requires a secret API key and/or secret creds The task for calling out to Foreman for targets uses the API and requires a username/password to authenticate. version: 2 config: ssh: _plugin: task task: vault::bolt_ssh_config_lookup parameters: token: _plugin: pkcs7 value: super secret thing winrm: _plugin: task task: vault::bolt_winrm_config_lookup parameters:
Jira (BOLT-1470) Plugin parameters can't use other plugins to get data
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1470 Plugin parameters can't use other plugins to get data Issue Type: Task Assignee: Unassigned Created: 2019/07/11 8:15 AM Priority: Normal Reporter: Lucy Wyman Builtin plugins can't use other plugins to populate their data values. For example, the parameters key for the task plugin can't use the prompt or pkcs7 plugins to hide secret parameters. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1469) Support remote state for terraform inventory plugin
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1469 Support remote state for terraform inventory plugin Issue Type: Task Assignee: Unassigned Created: 2019/07/11 8:01 AM Priority: Normal Reporter: Lucy Wyman The terraform plugin currently only supports local state. Should we support remote statefiles as well? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1454) Bolt is super slow
Title: Message Title Cyril Cordoui commented on BOLT-1454 Re: Bolt is super slow We are on RHEL7.6, 128G of ram, 24 threads, the authentication is done through ssh keys (on the three tools used in the benchmark) When you run the test on your box, is bolt using multiple cores? because it seems to be the bottleneck from what we observed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.315226.1562163484000.12097.1562842920097%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title Dimitri Tischenko commented on BOLT-1466 Re: Inventory configuration precedence is confusing Just tested a work-around by placing the pcp group at the top of the inventory file. This effectively forces bolt to use the pcp transport for the nodes from puppetdb, but it creates an inverse problem: now, the transport for nodes defined further down in the inventoryfile is ignored - all nodes which are also member of the pcp group now connect over pcp. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.315922.1562780625000.12070.1562836440086%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title
Dimitri Tischenko commented on BOLT-1466
Re: Inventory configuration precedence is confusing
The confusion arises especially with dynamically populated groups. For instance, if using this group:
targets:
- _plugin: puppetdb
query: "nodes[] { }"
config:
transport: pcp
one would assume that all targets dynamically acquired by the puppetdb plugin will be guaranteed to connect over pcp. However, due to the way inventory parsing is implemented, if that node name is defined elsewhere in the inventory file with a different transport, bolt will prefer that definition which is not what the user expects.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title Kevin Reeuwijk commented on BOLT-1466 Re: Inventory configuration precedence is confusing Shouldn't the (expected) behavior be that if -n groupname is specified, that Bolt scopes its use of the inventoryfile to that group only? Maybe the --nodes parameter is too ambiguous for this to work reliably, and a --group parameter is needed to more clearly communicate intent? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.315922.1562780625000.12035.1562834880198%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1467) bolt_shim::command should execute via powershell on Windows
Title: Message Title Kevin Reeuwijk commented on BOLT-1467 Re: bolt_shim::command should execute via powershell on Windows If this gets resolved, the work should be shared with the puppetlabs/exec module so that we can finally get this module to natively support Powershell as well. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315975.1562793707000.12033.1562834640087%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1207) Bolt should inform users when there is a new version available
Title: Message Title Kevin Reeuwijk commented on BOLT-1207 Re: Bolt should inform users when there is a new version available bolt update check would be a non-intrusive way of getting easy access to the desired info. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.301658.1553614758000.12030.1562834520267%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3802) pacman provider's yaourt support now totally broken
Title: Message Title Gabriel Nagy commented on PUP-3802 Re: pacman provider's yaourt support now totally broken Hi Antony Jordan, this is quite an old ticket and we're not sure we want to keep supporting yaourt, as it is not even mentioned anymore on the AUR helpers wiki page and many users have complained about security issues regarding it. If you'd like to implement support for a different AUR helper such as yay (which is in active development), please open a ticket with that in scope. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.62743.1420081435000.12003.1562830980147%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1935) Facter ipaddress6 on Windows returns link-local address with interface identifier
Title: Message Title Simon Thomson created an issue Facter / FACT-1935 Facter ipaddress6 on Windows returns link-local address with interface identifier Issue Type: Bug Affects Versions: FACT 3.11.8 Assignee: Unassigned Components: Windows Created: 2019/07/11 12:06 AM Priority: Normal Reporter: Simon Thomson When run on Windows servers "facter ipaddress6" returns the ipv6 address including the interface identifier. This causes issues with Ruby applications importing Puppet Facts as Ruby IPAddr cannot deal with IPv6 addresses that include the interface identifier. When run on Linux servers "facter ipaddress6" does not return the ipv6 address including the interface identifier. Examples: Windows Server 2012R2 Facter 3.11.6 PS C:\Users\user> facter ipaddress6 fe80:::xxx::bbe%13 CentOS 7.5.1804 Facter 3.11.8 [root@hostname ~]# facter ipaddress6 fe80::xxx:::d4bc /var/log/foreman/production.log 2019-07-09T14:59:12 [W|app|47240] Action failed IPAddr::InvalidAddressError: invalid address /opt/rh/rh-ruby25/root/usr/share/ruby/ipaddr.rb:649:in `in6_addr' /opt/rh/rh-ruby25/root/usr/share/ruby/ipaddr.rb:586:in `initialize' /usr/share/foreman/app/models/subnet.rb:295:in `new' /usr/share/foreman/app/models/subnet.rb:295:in `subnet_for' /usr/share/foreman/app/models/host/base.rb:466:in
Jira (FACT-1934) Add OpenSSH host keys to core facts for Windows
Title: Message Title Glenn Sarti updated an issue Facter / FACT-1934 Add OpenSSH host keys to core facts for Windows Change By: Glenn Sarti Acceptance Criteria: * When OpenSSH Server is installed on Windows Desktop (typically 10 ) and Serve Windows Server (e.g. 2019 ) , the host SSH public keys should appear in the core facts Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.316044.1562825377000.11983.1562826780170%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1934) Add OpenSSH host keys to core facts for Windows
Title: Message Title Glenn Sarti commented on FACT-1934 Re: Add OpenSSH host keys to core facts for Windows Done. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.316044.1562825377000.11984.1562826780176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1934) Add OpenSSH host keys to core facts for Windows
Title: Message Title Dirk Heinrichs commented on FACT-1934 Re: Add OpenSSH host keys to core facts for Windows Could the acceptance criteria be broadened a bit, please? It can also be installed on earlier Windows (Server) versions, by means of this Github project. In fact, I'm running it on systems as old as Server 2008R2. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "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.316044.1562825377000.11981.1562826060082%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1934) Add OpenSSH host keys to core facts for Windows
Title: Message Title Glenn Sarti created an issue Facter / FACT-1934 Add OpenSSH host keys to core facts for Windows Issue Type: Improvement Assignee: Unassigned Created: 2019/07/10 11:09 PM Environment: Windows 10/Server 2019 Labels: windows Priority: Normal Reporter: Glenn Sarti The Microsoft port of OpenSSH is now part of the Windows operating system for Windows Server 2019 and Windows 10 https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse The core facts for ssh should now also look in the default Windows location for the host keys %ALLUSERSPROFILE%\ssh\... and populate the facts. Recommendation from puppet-users https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/puppet-users/-irkkbzrUZw/wPR9o8QHDAAJ Add Comment
