Hide Forgot
Description of problem: Creation of VM from template with "Mount Windows guest tools" checkbox unchecked yields VM with "Mount Windows guest tools" checkbox checked. Version-Release number of selected component (if applicable): CNV 2.5.0 OCP 4.6 iib release tag 21980 How reproducible: Always Steps to Reproduce: 1. Create Template for Windows VMs 2. Deselect "Mount Windows guest tools" checkbox on first page 3. Create new VM from above template. Actual results: Mount Windows guest tools is checked in the new VM Expected results: Mount Windows guest tools should not be checked. Additional info:
Rastislav hi, The create VM from template was redesigned fixing lots of issues, I think this one was addressed too, When creating a VM from template in the new flow, user will get the template "as is" without changes (e.g. no guest agent disk, cloudinit changes, ...), Rastislav am I correct ?
@yzamir no, we still mount the guest agent (user have to go to advanced wizard if he doesnt want it mounted). Bug is still probably there, I didnt change much in advanced wizard.
> Bug is still probably there, ack
I just confirmed bug is still there in OpenShift Virtualization 2.5.1
Note: When fixing this bug look at this other bugs related to storage not using data available in the template to create storage in VM: https://bugzilla.redhat.com/show_bug.cgi?id=1911382 - source volumeMode (Block) and target volumeMode (Filesystem) do not match" shows in VM Error https://bugzilla.redhat.com/show_bug.cgi?id=1895169 - VM Template does not properly manage Mount Windows guest tools check box during VM creation (assigned Philip) https://bugzilla.redhat.com/show_bug.cgi?id=1911418 - The target storage class name is not displayed if default storage class is used (assigned Gilad)
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633