Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1350363

Summary: Improve error info "remote server timeout unexpectedly waiting for password prompt" when connect to a bogus server at p2v client
Product: Red Hat Enterprise Linux 7 Reporter: mxie <mxie>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 7.3CC: juzhou, mzhan, ptoscano, tzheng, xiaodwan
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: P2V
Fixed In Version: libguestfs-1.32.5-7.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 18:02:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description mxie@redhat.com 2016-06-27 09:29:28 UTC
Created attachment 1172817 [details]
screenshot

Description of problem:
Improve error info "remote server timeout unexpectedly waiting for password prompt" when connect to a bogus server at p2v client


Version-Release number of selected component (if applicable):
virt-p2v-1.32.5-6.el7
virt-v2v-1.32.5-6.el7.x86_64
libguestfs-1.32.5-6.el7.x86_64

How reproducible:
100%

Steps to Reproduce:

1. Boot the machine into p2v client via iso file
2. At the inputting conversion info interface,input bogus server info (the server's ip couldn't ping,such as 10.73.11.11) and then click test connection, the error will show: remote server timeout unexpectedly waiting for password prompt after waiting 1~2 mins,pls refer to screenshot


Actual results:
The error info is not very clear

Expected results:
Error message should be more explanatory, such as "ssh: connect to host 10.73.11.11 port 22: Connection timed out"


Additional info:

Comment 4 mxie@redhat.com 2016-06-28 10:26:27 UTC
Verify the bug with build
virt-p2v-1.32.5-7.el7

Steps:
1. Boot the machine into p2v client via iso file
2. At the inputting conversion info interface,input bogus server info (the server's ip couldn't ping,such as 10.73.11.11) and then click test connection, the error shows: ssh:connect to host 10.73.11.11 port 22 :Connection timed out

Result now: 
The error info is clear now, so the bug has been fixed

So move the bug from ON_QA to VERIFIED

Comment 6 errata-xmlrpc 2016-11-03 18:02:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2576.html