can't ssh to some w64 rev2 machines

RESOLVED FIXED

Status

Release Engineering
Platform Support
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: bhearsum, Assigned: Q)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
This error looks indicative of it being on to me:
➜  tmp  ssh cltbld@W64-IX-SLAVE93                                        
The authenticity of host 'w64-ix-slave93 (10.12.40.124)' can't be established.
RSA key fingerprint is c5:15:73:54:44:7f:00:00:17:10:f5:12:fa:69:75:b9.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'w64-ix-slave93' (RSA) to the list of known hosts.
Warning: the RSA host key for 'w64-ix-slave93' differs from the key for the IP address '10.12.40.124'
Offending key for IP in /home/bhearsum/.ssh/known_hosts:1088
Are you sure you want to continue connecting (yes/no)? yes
Received disconnect from 10.12.40.124: 10:
(Reporter)

Comment 1

4 years ago
I looked at w64-ix-slave160 after Armen couldn't get into it. This doesn't seem to be the case, thankfully. Updating summary.
Summary: check kpym config for ip banning on w64 rev2 slaves → can't ssh to some w64 rev2 machines

Comment 2

4 years ago
I can't ssh into any of the machines that I requested for re-image (e.g. w64-ix-slave160).

Q, markco: any ideas as why I can't ssh into newly re-imaged win64 machines?
(Assignee)

Updated

4 years ago
Assignee: nobody → q
(Assignee)

Comment 3

4 years ago
This had to do with some item level targeting to remove ssh keys from the builders per requests in other bugs. Since the KTS portion of our install doesn't affect those requests I reinstated it. cltbld should now support keys again as machines reboot.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.