So, adding the -o PubkeyAcceptedKeyTypes=+rsa-sha2-256,rsa-sha2-512 avoid the job to be stucked in the prompt password as Grebory mention, however, since scp now uses sftp protocol by default [1] the test still fails with cannot find /usr/libexec/sftp-server. This is a configuration that needs to be done on cirros side. From what I notice, the dropbear ssh server is not compiled with sftp support (then the /usr/libexec/sftp-server cannot be found).
According to [1] you can still use the old scp protocol passing the -O option, however, I don't know how to do it on the tempest side, I'm gonna need more research on that.
Also, this config must be set either on /etc/ssh/ssh_config or in /root/.ssh/config, and I'm not sure how this would affect other tests, or other playbooks that is running.
So, adding the -o PubkeyAcceptedK eyTypes= +rsa-sha2- 256,rsa- sha2-512 avoid the job to be stucked in the prompt password as Grebory mention, however, since scp now uses sftp protocol by default [1] the test still fails with cannot find /usr/libexec/ sftp-server. This is a configuration that needs to be done on cirros side. From what I notice, the dropbear ssh server is not compiled with sftp support (then the /usr/libexec/ sftp-server cannot be found).
According to [1] you can still use the old scp protocol passing the -O option, however, I don't know how to do it on the tempest side, I'm gonna need more research on that.
Also, this config must be set either on /etc/ssh/ssh_config or in /root/.ssh/config, and I'm not sure how this would affect other tests, or other playbooks that is running.
1 - https:/ /groups. google. com/g/opensshun ixdev/c/ LeaacTEj0j0? pli=1