Created attachment 1543465 [details] Screenshot for certificate information Description of problem: Expired "Digital Signatures" certificate for rhev-apt 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: 1. There is no error information during v2v conversion from vCenter to rhv4.3 # 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.6] Initializing the target -o rhv -os 10.66.144.40:/home/nfs_export [ 2.8] Opening the overlay [ 19.7] Inspecting the overlay [ 129.7] Checking for sufficient free disk space in the guest [ 129.7] Estimating space required on target for each disk [ 129.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. [ 159.4] Mapping filesystem data to avoid copying unused and blank areas [ 160.2] Closing the overlay [ 160.5] Checking if the guest needs BIOS or UEFI to boot [ 160.5] Assigning disks to buses [ 160.5] Copying disk 1/1 to /tmp/v2v.ap0YIl/c980b640-cb59-47f7-a0fe-90312d33deae/images/ca93c340-6f01-485f-b809-45d318d728f7/76588b2e-778a-4e2c-ae80-a25c981c4bc3 (raw) (100.00/100%) [1092.0] Creating output metadata [1092.1] Finishing off 2. Import the guest from export domain to data domain after v2v finishing conversion 3. Check rhev-apt.exe status 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, valid from 11/30/2015 to 12/30/2018 3.3 There is 0001-configure-rhev-apt.bat in c:/Program Files/Guestfs/Firstboot/scripts-done/ 3.4 RHEV-apt service is running by command "net start" 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: Fix it Additional info:
Verified on rhv-guest-tools-iso-4.3-6.el7ev.noarch Certificate is now valid till 1/25/2022
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:1054