action #94027
closedMTUI - traceback when connecting unavailable refhost
Description
Observation¶
critical: connecting to paris.qam.suse.cz failed: [Errno None] Unable to connect to port 22 on 10.100.192.47
warning: failed to add host paris.qam.suse.cz to target list
info: connecting to s390vsl020.suse.de
Exception: Error reading SSH protocol banner[Errno 104] Connection reset by peer
Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/paramiko/transport.py", line 2211, in _check_banner
buf = self.packetizer.readline(timeout)
File "/usr/lib/python3.8/site-packages/paramiko/packet.py", line 380, in readline
buf += self._read_timeout(timeout)
File "/usr/lib/python3.8/site-packages/paramiko/packet.py", line 607, in _read_timeout
x = self.__socket.recv(128)
ConnectionResetError: [Errno 104] Connection reset by peer
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/paramiko/transport.py", line 2039, in run
self._check_banner()
File "/usr/lib/python3.8/site-packages/paramiko/transport.py", line 2215, in _check_banner
raise SSHException(
paramiko.ssh_exception.SSHException: Error reading SSH protocol banner[Errno 104] Connection reset by peer
error: SSHException while connecting to craig.qam.suse.cz
critical: connecting to craig.qam.suse.cz failed: Error reading SSH protocol banner[Errno 104] Connection reset by peer
warning: failed to add host craig.qam.suse.cz to target list
Steps to reproduce¶
To be confirmed:
- Call
./mtui.py -s paris.qam.suse.cz -w 1
- Wait indefinitely?
- See the above error
Impact¶
Just cosmetic
Updated by okurz over 3 years ago
so you get a traceback along with the error when a host is not reachable. What expectations do you have how MTUI should behave?
Updated by vpelcak over 3 years ago
I expect getting the error in MTUI without any traceback.
Updated by okurz over 3 years ago
- Description updated (diff)
- Status changed from New to Feedback
- Assignee changed from osukup to okurz
- Priority changed from Normal to Low
- Target version changed from Ready to future
Adjusted the ticket description according to https://progress.opensuse.org/projects/openqav3/wiki/#Defects . I recommend to create tickets following such template as that can make reproduction and fixing easier for the developers. I also reduced the priority as I understand the impact is only cosmetic. Please correct me if I got that wrong though.
I tried to reproduce the error with
./mtui.py -s paris.qam.suse.cz -w 1
which yields
info: connecting to paris.qam.suse.cz
critical: connecting to paris.qam.suse.cz failed: [Errno 110] Connection timed out
warning: failed to add host paris.qam.suse.cz to target list
So this does not reproduce the error. Can you help me to provide "steps to reproduce"?
Updated by okurz over 3 years ago
Hi Vit,
okurz wrote:
[…] Can you help me to provide "steps to reproduce"?
I took a look myself and tried to reproduce the problem but could not find any tracebacks. Can you help me to find proper "steps to reproduce"?
Updated by okurz over 3 years ago
- Status changed from Feedback to New
- Assignee deleted (
okurz)
we need better "steps to reproduce" before we could fix the issue
Updated by vpelcak over 3 years ago
Hello.
I am no longer able to reproduce the issue.
I am using he development version of MTUI, so this was probably only temporary hiccup.
Feel free to close the issue. I will reopen if I manage to reproduce again.
Updated by okurz over 3 years ago
- Status changed from New to Rejected
- Assignee set to okurz
Feel free to close the issue. I will reopen if I manage to reproduce again.
Yes, sounds good. Please do so.