Bug 1688062

Test bug with builds:
kernel-4.18.0-83.el8.x86_64
virt-v2v-1.38.4-11.module+el8.1.0+3006+b7e94bb9.x86_64
libvirt-4.5.0-23.module+el8.1.0+2983+b2ae9c0a.x86_64
libguestfs-1.38.4-11.module+el8.1.0+3006+b7e94bb9.x86_64
virtio-win-1.9.7-3.el8.noarch
qemu-kvm-2.12.0-71.module+el8.1.0+3170+c76f9235.x86_64

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
[   1.8] Creating an overlay to protect the source from being modified
[   2.3] Initializing the target -o rhv -os 10.66.144.40:/home/nfs_export
[   3.2] Opening the overlay
[  30.3] Inspecting the overlay
[ 131.7] Checking for sufficient free disk space in the guest
[ 131.7] Estimating space required on target for each disk
[ 131.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/virtio-win/virtio-win.iso

The guest will be configured to use a basic VGA display driver.
virt-v2v: This guest has virtio drivers installed.
[ 157.6] Mapping filesystem data to avoid copying unused and blank areas
[ 158.5] Closing the overlay
[ 158.7] Checking if the guest needs BIOS or UEFI to boot
[ 158.7] Assigning disks to buses
[ 158.7] Copying disk 1/1 to /tmp/v2v.jDm3Wk/c980b640-cb59-47f7-a0fe-90312d33deae/images/a9bea880-cea5-4086-8540-f60cc098cb3b/7db863c4-bf19-4326-b09f-f41599021489 (raw)
    (100.00/100%)
[ 976.0] Creating output metadata
[ 976.1] 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.

Created attachment 1571468 [details]
certificate information

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/RHSA-2019:3345