Bug 1849915 - [v2v] VM import RHV to CNV: The timezone data is not available in the vm-import-controller image.
Summary: [v2v] VM import RHV to CNV: The timezone data is not available in the vm-imp...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: V2V
Version: 2.4.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.4.0
Assignee: Piotr Kliczewski
QA Contact: Ilanit Stein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-23 07:32 UTC by Ilanit Stein
Modified: 2020-07-28 19:10 UTC (History)
4 users (show)

Fixed In Version: v2.4.0-16
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-28 19:10:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:3194 0 None None None 2020-07-28 19:10:48 UTC

Description Ilanit Stein 2020-06-23 07:32:11 UTC
Description of problem:
Any VM import from RHV to CNV, both rom UI and API, fails on:

"The virtual machine could not be imported.
MappingRulesVerificationFailed: VM's timezone is not UTC-compatible. It should have offset of 0 and not observe DST"

Jakub Dżon:
It seems like downstream build bug - probably the timezone data is not 
available in the vm-import-controller image.

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

> $ oc get deploy -n openshift-cnv vm-import-operator -o yaml | grep image:
>                 f:image:{}
> image:registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-vm-import-rhel8-operator@sha256:fac8a99a2e04c3f0937e29004ec41f5678b9d165d 
> <http://registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-vm-import-rhel8-operator@sha256:fac8a99a2e04c3f0937e29004ec41f5678b9d165d>
> 2e1598e1cc3297e17fb240c
How reproducible:

Comment 1 Nelly Credi 2020-06-23 07:38:30 UTC
Removing regression flag, as this is a new feature, so by definition this is not a regression bug

Comment 3 Ilanit Stein 2020-06-28 06:24:10 UTC
Verified on CNV-2.4 from June 24 2020.

Comment 7 errata-xmlrpc 2020-07-28 19:10:33 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/RHSA-2020:3194


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