Support #40109
failed to lock machine in sepia lab
% Done:
0%
Tags:
Reviewed:
Affected Versions:
Description
I tried the following command:
teuthology-lock --lock-many 1 --machine-type smithi --os-type ubuntu --os-version 16.04
and got:
2019-06-02 12:01:15,864.864 ERROR:paramiko.transport:Exception: Error reading SSH protocol banner 2019-06-02 12:01:15,865.865 ERROR:paramiko.transport:Traceback (most recent call last): 2019-06-02 12:01:15,865.865 ERROR:paramiko.transport: File "/home/yuvalif/src/teuthology/virtualenv/local/lib/python2.7/site-packages/paramiko/transport.py", line 1749, in run 2019-06-02 12:01:15,865.865 ERROR:paramiko.transport: self._check_banner() 2019-06-02 12:01:15,865.865 ERROR:paramiko.transport: File "/home/yuvalif/src/teuthology/virtualenv/local/lib/python2.7/site-packages/paramiko/transport.py", line 1897, in _check_banner 2019-06-02 12:01:15,865.865 ERROR:paramiko.transport: raise SSHException('Error reading SSH protocol banner' + str(e)) 2019-06-02 12:01:15,865.865 ERROR:paramiko.transport:SSHException: Error reading SSH protocol banner
many times until maximum retries.
When I try to lock a VPS, i get:
2019-06-02 12:04:03,563.563 WARNING:teuthology.provision.downburst:Downburst not found! 2019-06-02 12:04:03,563.563 INFO:teuthology.provision.downburst:Using default values for supported os_type/os_version 2019-06-02 12:04:03,608.608 ERROR:teuthology.lock.ops:Insufficient nodes available to lock 1 vps nodes. 2019-06-02 12:04:03,608.608 ERROR:teuthology.lock.ops:{"message": "only 0 nodes available"}
History
#1 Updated by David Galloway over 4 years ago
- Status changed from New to 4
- Assignee set to David Galloway
This should be resolved. Can you confirm please?
#2 Updated by Kyrylo Shatskyy over 4 years ago
Looks like the issue with paramiko, it does not recognize your ssh key as valid, because in new format ssh-keygen uses "BEGIN OPENSSH PRIVATE KEY" in first line, but paramiko can only recognize keys in older format with "BEGIN RSA PRIVATE KEY" header. As workaround all keys should be generated with '-m PEM' option.
#3 Updated by David Galloway over 4 years ago
- Status changed from 4 to Resolved
Kyr is correct. See also https://wiki.sepia.ceph.com/doku.php?id=testnodeaccess#sshexceptionerror_reading_ssh_protocol_banner