Bug 1997668 - [v2v] VM import from RHV should not be blocked for a non UTC Timezone.
Summary: [v2v] VM import from RHV should not be blocked for a non UTC Timezone.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: V2V
Version: 4.8.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.8.2
Assignee: Sam Lucidi
QA Contact: Amos Mastbaum
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-25 15:57 UTC by Ilanit Stein
Modified: 2021-09-21 11:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-21 11:08:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt vm-import-operator pull 510 0 None None None 2021-09-02 21:11:18 UTC
Red Hat Product Errata RHSA-2021:3598 0 None None None 2021-09-21 11:08:54 UTC

Description Ilanit Stein 2021-08-25 15:57:40 UTC 
Description of problem:
With MTV 2.1.0 / CNV 4.8.z, VMIO blocks the migration of RHV VMs configured with a non-UTC timezone.

 - lastHeartbeatTime: "2021-08-12T16:02:24Z"
    lastTransitionTime: "2021-08-12T15:55:43Z"
    message: VM's timezone is not UTC-compatible. It should have offset of 0 and not observe DST
    reason: MappingRulesVerificationFailed
    status: "False"
    type: MappingRulesVerified

With "Fix clock timezone": https://github.com/kubevirt/kubevirt/pull/3973, Kubevirt supports setting the timezone in the VirtualMachine spec.

This means that during the migration of a virtual machine from RHV, the timezone can and must be kept.

Please allow (remove the current block in CNV-4.8.1) the VM import for VMs set to a non UTC timezone.

Version-Release number of selected component (if applicable):
CNV-4.8.1

Steps to Reproduce:
1. In RHV, create a virtual machine with a non-UTC timezone.
2. In MTV, create a plan, or in Openshift ->workloads->Virtualization page,
   for the newly created virtual machine.
3. Start the plan/Run the VM import.
4. Watch the VirtualMachineImport.
Comment 1 Ilanit Stein 2021-08-26 09:55:48 UTC 
If this bug verification will pass on CNV-4.8.2, 
MTV-2.1 docs will need to get updated that a VM with a non UTC TZ can be migrated.
Comment 3 Fabien Dupont 2021-09-07 20:27:34 UTC 
Please verify with hco-registry-bundle-container-v4.8.2-15 / iib:106992.
Comment 4 Amos Mastbaum 2021-09-09 15:37:06 UTC 
verified CNV-v4.8.2-18
it kept the time zone (VirtualMachineImport.spec.domain.timezone)
Comment 9 errata-xmlrpc 2021-09-21 11:08:02 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 (Moderate: OpenShift Virtualization 4.8.2 Images security and bug fix 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-2021:3598
Note You need to log in before you can comment on or make changes to this bug.