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 1688155 - Include of the updated rhev-apt in virt-v2v
Summary: Include of the updated rhev-apt in virt-v2v
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs
Version: 7.7
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard: V2V
Depends On: 1688062 1688157
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-13 09:58 UTC by zhoujunqin
Modified: 2019-08-06 12:45 UTC (History)
6 users (show)

Fixed In Version: libguestfs-1.40.2-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1688062
Environment:
Last Closed: 2019-08-06 12:44:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Certificate information (196.98 KB, image/png)
2019-04-29 03:15 UTC, liuzi 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:2096 0 None None None 2019-08-06 12:45:14 UTC

Description zhoujunqin 2019-03-13 09:58:48 UTC 
Since this issue should be always fixed on rhel7.7, so clone it to track, thanks.


+++ This bug was initially created as a clone of Bug #1688062 +++

Description of problem:
Include of the updated rhev-apt in virt-v2v after bug 1688056 fixed


Version-Release number of selected component (if applicable):
libvirt-4.5.0-23.module+el8+2800+2d311f65.x86_64
libguestfs-1.38.4-10.module+el8+2709+40ed2f2c.x86_64
virt-v2v-1.38.4-10.module+el8+2709+40ed2f2c.x86_64
qemu-kvm-2.12.0-63.module+el8+2833+c7d6d092.x86_64
virtio-win-1.9.7-3.el8.noarch
rhv: Software Version:4.3.0.1-0.1.el7

How reproducible:
100%

Steps to Reproduce:
Same with https://bugzilla.redhat.com/show_bug.cgi?id=1688056#c0

Actual results:
Certificate of rhev-apt.exe is expired(valid from 11/30/2015 to 12/30/2018), and there is no warning message prompts to users on windows guest.

Expected results:
Update virt-v2v related part after bug 1688056 fixed.


Additional info:
Comment 3 liuzi 2019-04-29 03:14:58 UTC 
Verify bug with builds:
virt-v2v-1.40.2-3.el7.x86_64
libvirt-4.5.0-12.el7.x86_64
libguestfs-1.40.2-3.el7.x86_64
qemu-kvm-rhev-2.12.0-26.el7.x86_64
virtio-win-1.9.7-0.el7.noarch
rhv-guest-tools-iso-4.3-6.el7ev.noarch

Steps:
1. Use virt-v2v to convert a windows guest from vmware to rhv;
# virt-v2v -ic vpx://root.73.141/data/10.73.75.219/?no_verify=1 esx6.7-win10-i386  --password-file /tmp/passwd -o rhv -os 10.66.144.40:/home/nfs_export -on esx6.7-win10-i386-bug1644277
[   0.0] Opening the source -i libvirt -ic vpx://root.73.141/data/10.73.75.219/?no_verify=1 esx6.7-win10-i386
[   2.0] Creating an overlay to protect the source from being modified
[   2.8] Opening the overlay
[  20.9] Inspecting the overlay
[ 123.7] Checking for sufficient free disk space in the guest
[ 123.7] Estimating space required on target for each disk
[ 123.7] Converting Windows 10 Enterprise to run on KVM
virt-v2v: warning: /usr/share/virt-tools/pnp_wait.exe is missing.  
Firstboot scripts may conflict with PnP.
virt-v2v: warning: there is no QXL driver for this version of Windows (10.0 
i386).  virt-v2v looks for this driver in 
/usr/share/rhv-guest-tools-iso/rhv-tools-setup.iso

The guest will be configured to use a basic VGA display driver.
virt-v2v: This guest has virtio drivers installed.
[ 150.7] Mapping filesystem data to avoid copying unused and blank areas
[ 152.3] Closing the overlay
[ 152.8] Assigning disks to buses
[ 152.8] Checking if the guest needs BIOS or UEFI to boot
[ 152.8] Initializing the target -o rhv -os 10.66.144.40:/home/nfs_export
[ 153.0] Copying disk 1/1 to /tmp/v2v.zRVBJ0/c980b640-cb59-47f7-a0fe-90312d33deae/images/1fa04a09-4f82-41bf-8d8e-bb6a510ac071/fc9f4392-1e1c-4888-91b7-560a3412e7f3 (raw)
    (100.00/100%)
[1106.8] Creating output metadata
[1106.9] Finishing off

2. Import the guest from export domain to data domain after v2v finishing conversion

3. Check rhev-apt certificate info in guest
3.1 There is rhev-apt.exe under C:\ drive
3.2 Left click rhev-apt to open properties, click digital signatures->details-> view certificate, certificate is now valid till 1/26/2022,pls refer to screenshot：certificate information.

Result:Certificate of rhev-apt.exe is valid from 11/27/2018 to 1/26/2022,so change bug from ON_QA to VERIFIED.
Comment 4 liuzi 2019-04-29 03:15:42 UTC 
Created attachment 1559726 [details]
Certificate information
Comment 6 errata-xmlrpc 2019-08-06 12:44:47 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://access.redhat.com/errata/RHEA-2019:2096
Note You need to log in before you can comment on or make changes to this bug.