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 1348900

Summary: virt-p2v should update error prompt when 'Test connection' with a non-existing user in conversion server
Product: Red Hat Enterprise Linux 7 Reporter: zhoujunqin <juzhou>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.3CC: mxie, mzhan, ptoscano, tzheng
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: P2V
Fixed In Version: libguestfs-1.32.5-6.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 18:01:48 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:

Description zhoujunqin 2016-06-22 09:32:48 UTC
Description of problem:
virt-p2v should update error prompt when 'Test connection' with a non-existing user in conversion server

Version-Release number of selected component (if applicable):
virt-p2v-1.32.5-5.el7.iso

How reproducible:
100%

Steps to Reproduce:
1. Boot the source machine into p2v client via iso
2. Input correct conversion server ip with a non-existing user in 'User name' and some word in 'Password' items, then press the 'Test Connection' button.


Actual results:
After 'Test Connection' finished, we get a error message:
unexpected password prompt:probably
the password supplied is wrong

It's a blur message for users, since it's same with test with (existing user+invalid password), cannot see any error about user is not existing.


Expected results:
It should update with clear prompt, such as 'username is wrong'.

Additional info:

Comment 1 Richard W.M. Jones 2016-06-22 09:54:06 UTC
Fixed in upstream commit c44ff0b789b782d9cee385f1f0193f804287a945.

Comment 4 mxie@redhat.com 2016-06-27 08:10:27 UTC
I can reproduce the bug with build
virt-p2v-1.32.5-5.el7

Verify the bug with build:
virt-p2v-1.32.5-6.el7

Steps:
1. Boot the machine into p2v client via iso file
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: Login failed:Probably the username and/or password is wrong

Result now:
The error info shows correct, so the bug has been fixed

So move the bug from ON_QA to VERIFIED

Comment 6 errata-xmlrpc 2016-11-03 18:01:48 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