The goal is to create SSH connection between 2 hosts, the Robot tests is executed on Windows 10. Robot Framework 5.1b2, SSH library 3.8.0
The same test is executing on Linux and Windows targets, they are both needed to open an SSH session on another Linux machine.
Before executing, the test verifies that “known_hosts” file is deleted so the next response to the ssh will be signature verification. Succeed on Linux while Windows display error: Write ${ConnectCommand} 18:56:05:No match found for ’ ’ in 10 seconds Output: [10X]0;Administrator: C:\Windows\system32\conhost.exessh root@10.10.20.10.
You could try to not use the Read Until Prompt, because it seems to be the failure cause.
Or, experiment changing the prompt to ‘:’ because that is the end of the output.
Other thing to consider is the timeout. Is 10 seconds enough time?
Well, I a have a similar setup (I don’t set the prompt): Open Connection ${host_under_test} port=22 width=160 height=80 alias=jumphost Login With Public Key (...) Write ssh -o StrictHostKeyChecking=no (...)
The output of Linux compared to Windows is different (see below), my next step will be to try using RF 6.1
Linux output Write ssh -o StrictHostKeyChecking=no root@10.10.20.10
Output} = ssh -o StrictHostKeyChecking=no root@10.10.20.10 Read delay=5s
Warning: Permanently added ‘10.10.205.10’ (ECDSA) to the list of known hosts. root@10.10.205.10’s password:
${Output} = Warning: Permanently added ‘10.10.20.10’ (ECDSA) to the list of known hosts. root@10.10.20.10’s password: Write passwordx
${Output} = Read delay=5s
Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-149-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support: Ubuntu Pro | Ubuntu 225 updates can be installed immediately. 0 of these updates are security updates. To see these additional updates run: apt list --upgradable New release ‘22.04.3 LTS’ available. Run ‘do-release-upgrade’ to upgrade to it. *** System restart required *** Last login: Mon Jan 29 15:08:56 2024 from 172.20.6.19 root@Int10:~#
Could you elaborate a bit more how you fixed your issue ?
I understood that you installed Cygwin on your Windows destination.
Did you also have to change the OpenSSH configuration to point at Cygwin and define it as the default shell ?