This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 1988279 - Virt-v2v can't remove vmware-tools 11.0.5 successfully from win2019 and win10 guest after conversion
Summary: Virt-v2v can't remove vmware-tools 11.0.5 successfully from win2019 and win1...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virt-v2v
Version: 9.0
Hardware: x86_64
OS: Unspecified
medium
low
Target Milestone: beta
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 1988442 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-30 09:15 UTC by mxie@redhat.com
Modified: 2023-09-22 17:32 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 17:32:12 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
virt-v2v-win2019-vmware-tools-rhel9.log (2.12 MB, text/plain)
2021-07-30 09:15 UTC, mxie@redhat.com 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7487 0 None Migrated None 2023-09-22 17:32:09 UTC

Description mxie@redhat.com 2021-07-30 09:15:48 UTC 
Created attachment 1809314 [details]
virt-v2v-win2019-vmware-tools-rhel9.log

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.45.2-1.el9.x86_64
libguestfs-1.45.6-10.el9.x86_64
guestfs-tools-1.46.1-3.el9.1.x86_64
libvirt-libs-7.5.0-1.el9.x86_64
qemu-kvm-6.0.0-10.el9.x86_64
nbdkit-1.26.2-1.el9.1.x86_64
virtio-win-1.9.15-3.el9.noarch


How reproducible:
100%

Steps to Reproduce:
1.Prepare a win2019 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-win2019-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 -v -x |& tee > virt-v2v-win2019-vmware-tools-rhel9.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"win2019-vmware-tools-after-rhel9-v2v.png"

Test the other windows guests (except win2012r2 because can't install vmware-tools for win2012r2 guest on vSphere 7.0 client) which have installed vmware-tools 11.0.5.15389592 from ESXi7.0 to rhv by v2v 

            VMware-tools uninstall
win2016      Success
win10 x64    Fail
win2012      Success
win8.1 x64   Success


Actual results:
As above description


Expected results:
Virt-v2v can remove vmware-tools successfully from all windows guest after conversion


Additional info:
1.Can reproduce the bug on rhel8.5 AV:
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

2.Can reproduce the bug on rhel8.4 AV:
virt-v2v-1.42.0-9.module+el8.4.0+9561+069bb9c1.x86_64
libguestfs-1.44.0-2.module+el8.4.0+10146+75917d2f.x86_64
libvirt-libs-7.0.0-14.1.module+el8.4.0+11095+d46acebf.x86_64
qemu-kvm-5.2.0-16.module+el8.4.0+10806+b7d97207.x86_64
nbdkit-1.24.0-1.module+el8.4.0+9341+96cf2672.x86_64
Comment 3 Richard W.M. Jones 2021-07-30 12:55:21 UTC 
I'm fairly sure this must happen because the fix for bug 1917760
is incomplete.  In that bug we replaced the wrong /i option with /x.
I can see from the log file that we are doing that here.  But
somehow we're getting the 1603 error which indicates that msiexec
is still trying to install VMware Tools.

While researching this I found this interesting VMware KBase article
about how to nuke VMware from the system.  We could try this as an
alternative to using msiexec since that tool seems to be broken.

https://kb.vmware.com/s/article/1001354
Comment 4 Richard W.M. Jones 2021-07-30 13:07:36 UTC 
The error from the log is:

CustomAction VM_LogStart returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

It appears that VMware Tools often doesn't uninstall, see someone
having the same problem here:
https://superuser.com/questions/1538084/uninstall-of-vmware-tools-fails-does-nothing

I think the KB based approach above may be better.
Comment 5 Klaus Heinrich Kiwi 2021-08-06 13:36:04 UTC 
Downgrading sev/prio based on the availability of workarounds (I also fail to see a critical functional issue here).

Should we make this bug a KB / documentation permanent restriction article?
Comment 6 Richard W.M. Jones 2021-08-06 13:39:23 UTC 
> Should we make this bug a KB / documentation permanent restriction article?

Not sure what that means, but this does need some development and
testing work to see if the approach of modifying the registry directly
(comment 3) would work better.
Comment 7 Klaus Heinrich Kiwi 2021-08-06 13:56:47 UTC 
(In reply to Richard W.M. Jones from comment #6)
> > Should we make this bug a KB / documentation permanent restriction article?
> 
> Not sure what that means, but this does need some development and
> testing work to see if the approach of modifying the registry directly
> (comment 3) would work better.

It would mean in practice that we won't try to solve a VMWare-tools bug from our end, but document the workaround for customers to do that themselves...

If there's a reliable way we can avoid that, though, I agree we should pursue that. Just hope we don't 'invalidate' any Windows-related support / guarantees (I guess we really don't care about VMWare here, do we?) by editing the registry directly. But I take it we do that elsewhere as well..
Comment 8 Klaus Heinrich Kiwi 2021-09-08 20:17:57 UTC 
*** Bug 1988442 has been marked as a duplicate of this bug. ***
Comment 15 RHEL Program Management 2023-09-22 17:31:18 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 16 RHEL Program Management 2023-09-22 17:32:12 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.