Jira (BOLT-1127) Bolt should echo port if custom SSH port is used

0 views
Skip to first unread message

David Alexander (JIRA)

unread,
Feb 12, 2019, 7:08:03 PM2/12/19
to puppe...@googlegroups.com
David Alexander created an issue
 
Puppet Task Runner / Improvement BOLT-1127
Bolt should echo port if custom SSH port is used
Issue Type: Improvement Improvement
Assignee: Unassigned
Created: 2019/02/12 4:07 PM
Priority: Normal Normal
Reporter: David Alexander

When connecting to the same IP address with Bolt, the output appears as follows:

[puppet@da-rhel-wks-01 ~]$ bolt command run uptime --nodes ro...@127.0.0.1:32768,ro...@127.0.0.1:32769,ro...@127.0.0.1:32770
Started on 127.0.0.1...
Started on 127.0.0.1...
Started on 127.0.0.1...
Finished on 127.0.0.1:
{{ STDOUT:}}
{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}
Finished on 127.0.0.1:
{{ STDOUT:}}
{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}
Finished on 127.0.0.1:
{{ STDOUT:}}
{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}
Successful on 3 nodes: ro...@127.0.0.1:32768,ro...@127.0.0.1:32769,ro...@127.0.0.1:32770
Ran on 3 nodes in 0.24 seconds

 

There is no way to tell which node is which. This is mildly problematic with Docker containers, but is very problematic where PAT is being used between networks and multiple nodes are being targeted.

 

Ideally, the output would appear as this:

 

[puppet@da-rhel-wks-01 ~]$ bolt command run uptime --nodes ro...@127.0.0.1:32768,ro...@127.0.0.1:32769,ro...@127.0.0.1:32770
Started on 127.0.0.1...
Started on 127.0.0.1...
Started on 127.0.0.1...
Finished on 127.0.0.1:32768:
{{ STDOUT:}}
{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}
Finished on 127.0.0.1:32769:
{{ STDOUT:}}
{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}
Finished on 127.0.0.1:32770:
{{ STDOUT:}}
{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}
Successful on 3 nodes: ro...@127.0.0.1:32768,ro...@127.0.0.1:32769,ro...@127.0.0.1:32770
Ran on 3 nodes in 0.24 seconds

 

Alternatively, it would be good to have a syntax switch in the --nodes parameter such that an alias could be passed - e.g.

 

[puppet@da-rhel-wks-01 ~]$ bolt command run uptime --nodes ro...@127.0.0.1:32768{node1},ro...@127.0.0.1:32769{node2},ro...@127.0.0.1:32770{node3}
Started on node1...
Started on node2...
Started on node3...
Finished on node1:
{{ STDOUT:}}
{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}
Finished on node2:
{{ STDOUT:}}
{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}
Finished on node3:
{{ STDOUT:}}
{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}
Successful on 3 nodes: ro...@127.0.0.1:32768{node1},ro...@127.0.0.1:32769{node2},ro...@127.0.0.1:32770{node3}
Ran on 3 nodes in 0.24 seconds

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Nick Lewis (JIRA)

unread,
Feb 12, 2019, 7:13:02 PM2/12/19
to puppe...@googlegroups.com
Nick Lewis updated an issue
Change By: Nick Lewis
Sprint: Bolt Ready for Grooming

Nick Lewis (JIRA)

unread,
Feb 12, 2019, 7:13:03 PM2/12/19
to puppe...@googlegroups.com

Alex Dreyer (JIRA)

unread,
Mar 25, 2019, 2:22:03 PM3/25/19
to puppe...@googlegroups.com
Alex Dreyer updated an issue
Change By: Alex Dreyer
Sprint: Bolt Ready for Grooming

Lucy Wyman (JIRA)

unread,
May 28, 2019, 12:28:03 PM5/28/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
Change By: Lucy Wyman


The real issue here is that 'uri' may not be displayable, so how can we compute a display name from the uri if the user doesn't specify a 'name'?
If you've specified a name we can use that as the display name.
Plan authors can print the display name with {{target.to_s}}
How can we ship this in a way that's safe for users on Inventory v1 to use?

David Alexander (JIRA)

unread,
May 30, 2019, 9:11:02 PM5/30/19
to puppe...@googlegroups.com
David Alexander commented on Improvement BOLT-1127
 
Re: Bolt should echo port if custom SSH port is used

If showing the name is too difficult Lucy Wyman just show the port as per my first example - at least this will allow easy differentiation between results.

Dylan Ratcliffe (JIRA)

unread,
Jul 10, 2019, 1:15:02 PM7/10/19
to puppe...@googlegroups.com

This would also be good for vagrant hosts which are much the same, all 127.0.0.1 with different ports

Reply all
Reply to author
Forward
0 new messages