Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Descriptionmxie@redhat.com
2021-07-30 14:44:00 UTC
Created attachment 1809435[details]
virt-v2v-win10-vmware-tools-11.0.5.log
This bug was initially created as a copy of Bug #1988279
Description of problem
Virt-v2v can't remove vmware-tools 11.0.5 successfully from win2019 and win10 guest after conversion
Version-Release number of selected component (if applicable):
virt-v2v-1.42.0-14.module+el8.5.0+11846+77888a74.x86_64
libguestfs-1.44.0-3.module+el8.5.0+10681+17a9b157.x86_64
libvirt-libs-7.5.0-1.module+el8.5.0+11664+59f87560.x86_64
qemu-kvm-6.0.0-25.module+el8.5.0+11890+8e7c3f51.x86_64
nbdkit-1.24.0-1.module+el8.4.0+9341+96cf2672.x86_64
virtio-win-1.9.17-3.el8_4.noarch
How reproducible:
100%
Steps to Reproduce:
1.Prepare a win10 guest which has installed vmware-tools 11.0.5.15389592 on Vmware environment and convert it from VMware to rhv by v2v
# virt-v2v -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk7.0.2 -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 esx7.0-win10-x86_64 -o rhv-upload -of qcow2 -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -ip /home/passwd -op /home/rhvpasswd -os nfs_data -b ovirtmgmt -on esx7.0-win10-x86_64-rhel8.5 -v -x |& tee > virt-v2v-win10-vmware-tools-11.0.5.log
2.Check the guest after v2v finishing conversion, found although vmware-tools service is stop, vmware-tools isn't removed from windows programs and exit code is 1603 of uninstalling vmware script in firstboot log, please refer to screenhost"win10-vmware-tools-11.0.5-after-rhel8.5-v2v.png"
Test the other windows guests which have installed vmware-tools 11.0.5.15389592 from ESXi7.0 to rhv by v2v (not test win2012r2 because can't install vmware-tools for win2012r2 guest on vSphere 7.0 client)
VMware-tools uninstall
win2019 Fail
win2016 Success
win2012 Success
win8.1 x64 Success
Actual results:
As above description
Expected results:
Virt-v2v can remove vmware-tools successfully from all windows guests after conversion
Additional info:
Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.
Comment 2Klaus Heinrich Kiwi
2021-09-08 20:17:57 UTC
(In reply to Eric Hadley from comment #1)
> Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8,
> then clone to the current RHEL8 release.
As we already had Bug 1988279 targeting RHEL9, closing this as a duplicate.
*** This bug has been marked as a duplicate of bug 1988279 ***