Bug 1227599

Summary: P2V invalid password prints unexpected end of file waiting for command prompt.
Product: Red Hat Enterprise Linux 7 Reporter: tingting zheng <tzheng>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: juzhou, mxie, mzhan, ptoscano, sherold, xiaodwan
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: P2V
Fixed In Version: libguestfs-1.32.5-4.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 17:53:18 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:
Bug Depends On:    
Bug Blocks: 1288337    

Description tingting zheng 2015-06-03 05:54:42 UTC
Description of problem:
 P2V error:unexpected end of file waiting for command prompt when wrong user/password for conversion server given

Version-Release number of selected component (if applicable):
libguestfs-1.28.1-1.37.el7.x86_64
virt-v2v-1.28.1-1.37.el7.x86_64
livecd-p2v-201505191242.iso	

How reproducible:
100%

Steps to Reproduce:
1.Launch virt-p2v client.
2.Input correct conversion server ip.
3.Input either wrong user name or password.
4.Click "Test connection",unexpected end of file waiting for command prompt shows.

Actual results:
As description.

Expected results:
More clear error info shows.

Additional info:

Comment 2 Richard W.M. Jones 2015-06-03 09:49:07 UTC
Duplicate of bug 1167916?

Comment 3 Richard W.M. Jones 2015-06-03 09:51:31 UTC
(In reply to Richard W.M. Jones from comment #2)
> Duplicate of bug 1167916?

OK I see you added that in the 'see also' field.  Is there any
reason to think this bug is different from bug 1167916?

Anyway I am able to reproduce this easily just by running
virt-p2v on my laptop and typing in the wrong root password.
So obviously bug 1167916 is not fixed even upstream.

Comment 4 tingting zheng 2015-06-03 10:06:28 UTC
(In reply to Richard W.M. Jones from comment #3)
> (In reply to Richard W.M. Jones from comment #2)
> > Duplicate of bug 1167916?
> 
> OK I see you added that in the 'see also' field.  Is there any
> reason to think this bug is different from bug 1167916?
> 
> Anyway I am able to reproduce this easily just by running
> virt-p2v on my laptop and typing in the wrong root password.
> So obviously bug 1167916 is not fixed even upstream.

I file this bug just from QE's side,as they are 2 scenarios with different error info.

Comment 6 Richard W.M. Jones 2016-06-16 20:25:53 UTC
Upstream fix 3dd3bba77837f011d6fd81cd6c3407341e4a30c7.

Comment 8 mxie@redhat.com 2016-06-22 10:40:44 UTC
I can reproduce the bug with build
virt-p2v-1.28.1-1.51.3.el7

Try to verify the bug with build
virt-p2v-1.32.5-5.el7


Steps:

scenario1:

1.1 Boot the machine into p2v client via iso file
1.2 At the inputting conversion info interface,input conversion server's correct ip but input wrong username or wrong password, then click test connection, the error shows:  unexpected password prompt:probably the password supplied is wrong

Result now:
The error info shows correct


scenario2:

2.1 Boot the machine into p2v client via iso file
2.2 At the inputting conversion info interface,input bogus server info (the server's ip couldn't ping) and then click test connection, the error shows: timeout waiting for password prompt

Result now:
The error info shows correct


scenario3:

3.1 Boot the machine into p2v client via iso file
3.2 At the inputting conversion info interface,input correct server info which has old virt-v2v or not installed virt-v2v,then click test connection, the error shows:virt-v2v is not installed on the conversion server,or it might be a too old version

Result now
The error info shows correct

According to above results, the bug has been fixed

So move the bug from ON_QA to VERIFIED

Comment 10 errata-xmlrpc 2016-11-03 17:53:18 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