Bug 1785528

Summary: Should remove info about "Remove VMware tools from Windows guests" in virt-v2v-input-vmware man page
Product: Red Hat Enterprise Linux Advanced Virtualization Reporter: mxie <mxie>
Component: libguestfsAssignee: Pino Toscano <ptoscano>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 8.1CC: juzhou, mzhan, 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-20.module+el8.2.0+5433+9e1420c8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-05 09:52:22 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:

Description mxie@redhat.com 2019-12-20 06:31:14 UTC
Description:
Should remove info about "Remove VMware tools from Windows guests" in virt-v2v-input-vmware man page

Version-Release number of selected component (if applicable):
virt-v2v-1.40.2-16.module+el8.1.1+5096+6326d3d5.x86_64

How reducible:
100%

Reproducing steps:
1. Check virt-v2v man page about Windows vmware-tools
# man virt-v2v-input-vmware |grep "Remove VMware tools from Windows guests" -A 10
   VMX: Remove VMware tools from Windows guests
       For Windows guests, you should remove VMware tools before conversion.
       Although this is not strictly necessary, and the guest will still be
       able to run, if you don't do this then the converted guest will
       complain on every boot.  The tools cannot be removed after conversion
       because the uninstaller checks if it is running on VMware and refuses
       to start (which is also the reason that virt-v2v cannot remove them).

       This is not necessary for Linux guests, as virt-v2v is able to remove
       VMware tools.

--
   OVA: Remove VMware tools from Windows guests
       For Windows guests, you should remove VMware tools before conversion.
       Although this is not strictly necessary, and the guest will still be
       able to run, if you don't do this then the converted guest will
       complain on every boot.  The tools cannot be removed after conversion
       because the uninstaller checks if it is running on VMware and refuses
       to start (which is also the reason that virt-v2v cannot remove them).

       This is not necessary for Linux guests, as virt-v2v is able to remove
       VMware tools.

--
   vCenter: Remove VMware tools from Windows guests
       For Windows guests, you should remove VMware tools before conversion.
       Although this is not strictly necessary, and the guest will still be
       able to run, if you don't do this then the converted guest will
       complain on every boot.  The tools cannot be removed after conversion
       because the uninstaller checks if it is running on VMware and refuses
       to start (which is also the reason that virt-v2v cannot remove them).

       This is not necessary for Linux guests, as virt-v2v is able to remove
       VMware tools.



Actual result:
there is info about "Remove VMware tools from Windows guests" in virt-v2v-input-vmware man page


Expected result:
Should remove info about "Remove VMware tools from Windows guests" in virt-v2v-input-vmware man page because v2v already can remove the vmware-tools from windows guest since version 1.40



Additional info:

Comment 3 mxie@redhat.com 2020-01-19 11:25:58 UTC
Verify the bug with builds:
virt-v2v-1.40.2-20.module+el8.2.0+5433+9e1420c8.x86_64
libguestfs-1.40.2-20.module+el8.2.0+5433+9e1420c8.x86_64


Steps:
1. Check virt-v2v man page about Windows vmware-tools
# man virt-v2v-input-vmware |grep "Remove VMware tools from Windows guests" -A 10
<standard input>:672: warning [p 8, 2.5i]: can't break line

Result:
  The info about "Remove VMware tools from Windows guests" has been deleted in virt-v2v-input-vmware man page, so move the bug from ON_QA to VERIFIED.

Comment 5 errata-xmlrpc 2020-05-05 09:52:22 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-2020:2017