Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1798425

Summary: Regression: KVM Importing fails due to an old version
Product: [oVirt] ovirt-engine Reporter: Steven Rosenberg <srosenbe>
Component: Backend.CoreAssignee: Andrej Krejcir <akrejcir>
Status: CLOSED CURRENTRELEASE QA Contact: Nisim Simsolo <nsimsolo>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4.0CC: akrejcir, bpelled, bugs, con_louca, nsimsolo, rbarry, sgoodman
Target Milestone: ovirt-4.4.0Keywords: Regression
Target Release: ---Flags: pm-rhel: ovirt-4.4+
pm-rhel: blocker?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine 4.4.0-26 b5b5c99ca2f Doc Type: Bug Fix
Doc Text:
Previously, importing virtual machines failed when the source version variable was null. With this update, validation of the source compatibility version is removed, enabling the import to succeed even when the source version variable is null.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-20 20:01:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1798175    
Bug Blocks: 1746699    
Attachments:
Description Flags
Screen shot of the version error none

Description Steven Rosenberg 2020-02-05 10:33:24 UTC 
Created attachment 1657876 [details]
Screen shot of the version error

Description of problem: When performing a KVM external import, the importing fails due to the following error:

"KVM_centos7.0_ISO: Cannot import VM. The version of imported VM is too old. Only VMs with version 3.6 or higher can be imported."

The failure occurs due to a change that attempts to validate the version, but when the source version is null, the import fails [1].


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


How reproducible:


Steps to Reproduce:
1. Within the Virtual Machine View of the engine, choose the more button and import.
2. Choose a KVM external import and choose next for both screens
3.

Actual results:

The KVM import fails with the above error.

Expected results:

The KVM Import should succeed.

Additional info:

[1] https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/utils/VmVersionUpdater.java#L184
Comment 1 RHEL Program Management 2020-02-06 02:21:31 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 3 Ryan Barry 2020-02-19 02:10:34 UTC 
*** Bug 1804135 has been marked as a duplicate of this bug. ***
Comment 4 Sandro Bonazzola 2020-03-20 16:54:15 UTC 
This bug is targeted to 4.4.1 and in modified state. can we re-target to 4.4.0 and move to QA?
Comment 5 Nisim Simsolo 2020-03-30 13:33:11 UTC 
Verifiaction builds:
ovirt-engine-4.4.0-0.29.master.el8ev
vdsm-4.40.9-1.el8ev.x86_64
libvirt-daemon-kvm-6.0.0-15.module+el8.2.0+6106+b6345808.x86_64
qemu-kvm-4.2.0-16.module+el8.2.0+6092+4f2391c1.x86_64
Comment 6 Sandro Bonazzola 2020-05-20 20:01:29 UTC 
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 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.