Jira (BOLT-583) Unable to use "localhost" as a node on Windows

[Glenn Sarti (JIRA)]

Title: Message Title

Glenn Sarti created an issue   Puppet Task Runner / BOLT-583 Unable to use "localhost" as a node on Windows Issue Type: Bug Affects Versions: BOLT 0.20.5 Assignee: Unassigned Created: 2018/06/12 8:25 PM Priority: Normal Reporter: Glenn Sarti When running a PowerShell task on a local computer with a correctly configured WinRM service, but with the target node of 'localhost' I get a message saying it's not supported and really obtuse error stack. Using a simple trick of --nodes '127.0.0.1' works around the issue. Note - The IP6 loopback ::1 does not work example C:\Source\puppetlabs-wsus_client [(f2ade67...) +1 ~0 -0 !]> bolt task run wsus_client::update_history --modulepath .\spec\fixtures\modules\ --nodes localhost --transport winrm --no-ssl --user ******** --password Please enter your password: C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/transport/local.rb:24:in `initialize': The local transport is not yet implemented on Windows (NotImplementedError) from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:25:in `new' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:25:in `block (2 levels) in initialize' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/delay.rb:87:in `block in value' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `block in synchronize' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/delay.rb:83:in `value' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/delay.rb:135:in `wait' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/concern/obligation.rb:87:in `wait!' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:39:in `transport' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:52:in `block in batch_execute' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:51:in `each' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:51:in `flat_map' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:51:in `batch_execute' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:161:in `block in run_task' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:101:in `log_action' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:157:in `run_task' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/bolt-modules/boltlib/lib/puppet/functions/run_task.rb:112:in `run_task_raw' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/vendored/puppet/lib/puppet/pops/functions/dispatch.rb:60:in `invoke' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:43:in `block in dispatch' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:42:in `catch' from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/vendored/puppet/lib/puppet/pops/functions/dispatcher.rb:42:in `dispatch' ... Either this should be implemented for Windows, or the local detection should be disabled on Windows so I can use "localhost" and not get a wall of error text. Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.