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.

Description of problem:
Error info is not clear when failed ssh to conversion server using non-root user with password on p2v client


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


How reproducible:
100%

Steps to Reproduce:
1.Configure non-root user run sudo with password
$ sudo whoami
[sudo] password for juzhou: 
juzhou is not in the sudoers file.  This incident will be reported.

2. Boot the source machine into p2v client via iso
3.After virt-p2v client launched, fill information as following:
Conversion server: 10.66.71.81 : 22
User name:juzhou(a non-root user)
Password:******
3.1 Check "Use sudo when running virt-v2v" button 
3.2 Press "Test connection" button

4.'Test connection' failed with error message:
virt-v2v is not installed on the conversion server, or it might be a too old version.
Details please see png-1.

 


Actual results:
As above description

Expected results:
Should give a clear failed reason when failed ssh to conversion server using non-root user with password on p2v client

Additional info:

Fixed upstream with commit
https://github.com/libguestfs/libguestfs/commit/5b6a8e086264c85fb048c0eadff6c34351663133

Also required:
https://github.com/libguestfs/libguestfs/commit/d41cf142e1eb285eca798889d3b6a955afffbe32
https://github.com/libguestfs/libguestfs/commit/5e794b86072cfaa1d2017d93bd3a24be72636c02

I can reproduce the bug with build
virt-p2v-1.32.5-5.el7

Try to verify this bug with build:
virt-p2v-1.32.5-6.el7


Steps:

1.Not add non-user with password in sudoers file 
# vim /etc/sudoers

## Allow root to run any commands anywhere 
root    ALL=(ALL)       ALL

2. Boot the source machine into p2v client via iso
3. After virt-p2v client launched, fill information as following:
Conversion server: 10.66.xx.xx : 22
User name:mxie(a non-root user)
Password:******
4. Check "Use sudo when running virt-v2v" button 
5. Press "Test connection" button and then error info show as
"sudo for user"mxie"requires a password.Edit/etc/sudoers on the conversion server to ensure the "NOPASSWD:"option is set for this user"

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

So move this bug from ON_QA to VERIFIED.

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