Jira (BOLT-344) Failed connections are no longer displayed on 'bolt command run'

[Michael Smith (JIRA)]

Title: Message Title

Michael Smith created an issue   Puppet Task Runner / BOLT-344 Failed connections are no longer displayed on 'bolt command run' Issue Type: Bug Affects Versions: BOLT 0.16.2 Assignee: Unassigned Created: 2018/02/20 2:50 PM Priority: Normal Reporter: Michael Smith When running bolt command run ... (I believe it would also affect script, file, and task operations) with a node configured with the wrong port, I no longer get a connection error. Instead it seems to silently succeed. For example, running bolt command run hostname -n node1,node2,node3:23 displays Started on node1... Started on node2... Started on node3... Finished on node1: STDOUT: node1 Finished on node2: STDOUT: node2 Ran on 3 nodes in 0.72 seconds The only signs of failure are missing output for node3, and that the exit code is 2. Previously it would have also included Failed on node3: Failed to connect to node3: Connection refused - connect(2) for node3:23 Add Comment   This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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.