+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1750482 +++ ====================================================================== Description of problem: Unable to create Windows VM from the VM Portal. Fails with the following error: ~~~ CREATE_VM failed [Cannot add VM. Invalid time zone for given OS type., Attribute: vmStatic] ~~~ Errors in the engine.log: ~~~ 2019-09-09 12:42:49,931-04 WARN [org.ovirt.engine.core.bll.AddVmFromScratchCommand] (default task-31) [eccd49e9-db7b-41a7-b532-f39a60c33466] Validation of action 'AddVmFromScratch' failed for user rhevtest.com-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_TIMEZONE,$groups [Ljava.lang.Class;@21962d5,$message ACTION_TYPE_FAILED_INVALID_TIMEZONE,$payload [Ljava.lang.Class;@17357b86,ACTION_TYPE_FAILED_ATTRIBUTE_PATH,$path vmStatic,$validatedValue org.ovirt.engine.core.common.businessentities.VmStatic@a72f3260 ~~~ The VM create for OS Linux are created without any errors. Version-Release number of selected component (if applicable): ~~~ ovirt-engine-4.3.5.4-0.1.el7.noarch ~~~ How reproducible: 100% Steps to Reproduce: 1. From the user VM portal, create a Windows VM. 2. 3. Actual results: Fails to create Windows VM. Expected results: Windows VM's should be created without any errors. Additional info: Windows VM can be created without any errors from the Administration Portal. (Originally by Bimal Chollera)
Verified in ovirt-engine-4.3.8.1-0.1.master.el7.noarch ovirt-web-ui-1.6.0-2.el7ev.noarch VMs with OS type Windows(*) can be successfully created in VM Portal. (*) tried with OS types: Windows XP, Windows 7, Windows 7 x64, Windows 10 x64, Windows 2003, Windows 2008 R2 x64, Windows 2019 x64. Verified with the following VM/template combinations: - VM from Blank template (template with default TZ GMT+0) - VM from Blank template (template TZ set to GMT-12) - VM from custom template (template TZ set GMT+0) - VM from custom template (template TZ set GMT-12)
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/RHSA-2020:0498
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days