Bug 1688157

Summary: Include of the updated rhev-apt in virt-v2v
Product: Red Hat Enterprise Linux Advanced Virtualization Reporter: zhoujunqin <juzhou>
Component: libguestfsAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: mxie, ptoscano, rjones, tzheng, xiaodwan, zili
Target Milestone: rc   
Target Release: 8.0   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: V2V
Fixed In Version: libguestfs-1.40.2-2.module+el8.0.1+2990+fb52aff8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1688062 Environment:
Last Closed: 2019-08-07 10:41:10 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: 1688062    
Bug Blocks: 1688155    
Attachments:
Description Flags
Certificate information none

Description zhoujunqin 2019-03-13 10:03:39 UTC
This issue should be always fixed on rhel8 fast train, 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 2 liuzi 2019-05-13 07:12:16 UTC
Verify bug with builds:
kernel-4.18.0-80.el8.x86_64
virt-v2v-1.40.2-3.module+el8+3153+f1590ef7.x86_64
libvirt-5.0.0-7.module+el8+3023+072e7fc8.x86_64
libguestfs-1.40.2-3.module+el8+3153+f1590ef7.x86_64
virtio-win-1.9.7-3.el8.noarch
qemu-kvm-3.1.0-25.module+el8+3153+f1590ef7.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.9] Creating an overlay to protect the source from being modified
[   2.4] Opening the overlay
[  47.4] Inspecting the overlay
[ 146.2] Checking for sufficient free disk space in the guest
[ 146.2] Estimating space required on target for each disk
[ 146.2] 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.
[ 171.2] Mapping filesystem data to avoid copying unused and blank areas
[ 172.2] Closing the overlay
[ 172.4] Assigning disks to buses
[ 172.4] Checking if the guest needs BIOS or UEFI to boot
[ 172.4] Initializing the target -o rhv -os 10.66.144.40:/home/nfs_export
[ 172.7] Copying disk 1/1 to /tmp/v2v.EDBiqA/c980b640-cb59-47f7-a0fe-90312d33deae/images/31097521-6637-4ef7-a5c6-18a6165f03a7/8fb434c4-f12c-49c6-9be9-5241f86cc82c (raw)
    (100.00/100%)
[ 908.6] Creating output metadata
[ 908.6] 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 3 liuzi 2019-05-13 07:13:06 UTC
Created attachment 1567803 [details]
Certificate information

Comment 5 errata-xmlrpc 2019-08-07 10:41:10 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/RHBA-2019:2395