cannot connect to linux spot instances

NEW
Assigned to

Status

Infrastructure & Operations
RelOps
17 days ago
14 days ago

People

(Reporter: kmoir, Assigned: dhouse)

Tracking

Details

(Reporter)

Description

17 days ago
I'm trying to connect to a linux spot instance to solve an issue

ssh -l cltbld bld-linux64-spot-092.build.releng.use1.mozilla.com
Duo two-factor login for kmoir

Enter a passcode or select one of the following options:

 1. Duo Push to XXX-XXX-3101

Passcode or option (1-1): 1
Stdio forwarding request failed: Session open refused by peer
ssh_exchange_identification: Connection closed by remote host

I have my local ssh config specified just like the mana page on jumphosts specified but I can't connect.  I tried a bunch of things in my ssh config but none have worked so if you could provide suggestions I would appreciated it.
(Reporter)

Comment 1

17 days ago
As an aside, the spot instance above terminated itself, but this is a general problem about sshing to spot instances.
(Assignee)

Comment 2

17 days ago
I'll test this.
Assignee: relops → dhouse
(Assignee)

Comment 3

14 days ago
I'm seeing the same behavior. I tested friday against one (and then all the spot instances were gone) and another today and the connection from the jumphost appears fine but the ssh fails. I think it is not finding the target host. If I use the IP, it works:

```
$ ssh -J rejh1.srv.releng.scl3.mozilla.com root@tst-linux64-spot-321.test.releng.usw2.mozilla.com
Stdio forwarding request failed: Session open refused by peer
ssh_exchange_identification: Connection closed by remote host
$ ssh -J rejh1.srv.releng.scl3.mozilla.com root@10.132.62.5
Last login: Mon Nov  6 10:45:03 2017 from rejh1.srv.releng.scl3.mozilla.com
This host is set to follow security level "low"
Unauthorized access prohibited
REBOOT REQUIRED: reboot_after_kernel_upgrade, reboot_after_puppet
[root@tst-linux64-spot-322.test.releng.usw2.mozilla.com ~]# exit
logout
Connection to 10.132.62.5 closed.
```
You need to log in before you can comment on or make changes to this bug.