Bug 1999651 - Importing Windows VMs with timezone 'US Eastern Standard Time' from OVA that was exported from previous versions fails
Summary: Importing Windows VMs with timezone 'US Eastern Standard Time' from OVA that ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.4.8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.4.9
: ---
Assignee: Saif Abusaleh
QA Contact: Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-31 13:48 UTC by Saif Abusaleh
Modified: 2021-10-21 07:27 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-4.4.9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-21 07:27:14 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.4+
pm-rhel: blocker?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-43338 0 None None None 2021-08-31 13:52:37 UTC
oVirt gerrit 116260 0 None None None 2021-09-02 15:26:03 UTC
oVirt gerrit 116272 0 None None None 2021-09-02 15:26:03 UTC
oVirt gerrit 116372 0 None MERGED engine: fix wrong time zone mapping 2021-09-14 08:12:11 UTC
oVirt gerrit 116691 0 ovirt-engine-4.4 MERGED engine: fix wrong time zone mapping 2021-09-14 15:11:16 UTC

Description Saif Abusaleh 2021-08-31 13:48:53 UTC
Description of problem:when importing Windows  VM with US Eastern Standard Time from OVA with version below 4.7, import fails



How reproducible:


Steps to Reproduce:
1.Export Windows VM to OVA that have US Eastern Standard Time timezone in version 4.4.6 for example
2. upgrade to version >= 4.4.7
3. import the VM

Actual results:

import fails with:

    Cannot import VM. Invalid time zone for given OS type.
    Attribute: vm.vmStatic


Expected results:
VM to be imported successfully, and time zone to be changed to Eastern Standard Time


Additional info:

US Eastern Standard Time time zone got removed in 4.4.7, and there is no mapping to equivalent time zone Eastern Standard time

there is two workarounds that cane be done in order to fix the issue:

option 1- Change the existing VM's that is failing to default time-zone and try to do the process again

option 2- Extend the time-zones list and add the time-zone that is missing
in order to do that need to follow the instructions here and then add this time zone line:
America/Indianapolis=US Eastern Standard Time
then restart the engine

Comment 1 Arik 2021-09-02 11:50:09 UTC
An easy workaround is to fix the typo in /usr/share/ovirt-engine/conf/timezones-defaults.properties or overriding  Europe/Warsaw with a fixed value in a separate properties file

Comment 3 RHEL Program Management 2021-09-06 07:20:00 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 4 Tamir 2021-10-03 12:54:30 UTC
Verified on RHV 4.4.9-2. All looks good to me.

Env:
  - Engine instance with RHV 4.4.9-2 (ovirt-engine-4.4.9-0.6.el8ev) and RHEL 8.5 installed.
  - 3 Hosts with RHV 4.4.9-2 and RHEL 8.5, vdsm-4.40.90.1-1.el8ev

Steps:

* Exported a Windows 10 VM with US Eastern Standard Time timezone set to OVA from RHV-4.4.6-6 (ovirt-engine-4.4.6.6-0.10.el8ev.noarch)


In the RHV 4.4.9-2 instance:

In Admin Portal:

1. Create a 4.6 data center and a 4.6 cluster.
2. Add the hosts and NFS data domains. 
3. Import the VM from the exported OVA.


Results (As Expected):
1. The 4.6 data center and a 4.6 cluster were created.
2. The host and data domain were added.
3. The VM was imported successfully with timezone (GMT-05:00) Eastern Standard Time.

Comment 5 Sandro Bonazzola 2021-10-21 07:27:14 UTC
This bugzilla is included in oVirt 4.4.9 release, published on October 20th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.9 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.