Bug 1364164 - Import KVM guest image: cannot import VM as clone
Summary: Import KVM guest image: cannot import VM as clone
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.0.2.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.0.4
: 4.0.4
Assignee: Shahar Havivi
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-04 15:07 UTC by Nisim Simsolo
Modified: 2017-03-20 20:48 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-26 12:35:42 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.0.z+
mgoldboi: planning_ack+
tjelinek: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)
engine.log.gz issue occured at: 2016-08-04 18:02:14,499 (976.55 KB, application/x-gzip)
2016-08-04 15:12 UTC, Nisim Simsolo 		no flags Details
vdsm.log.gz (142.33 KB, application/x-gzip)
2016-08-04 15:13 UTC, Nisim Simsolo 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1302427 0 high CLOSED [RFE] Add ability to import RHEL KVM guest images (managed by libvirt) directly into RHEV 2021-08-30 12:34:14 UTC
oVirt gerrit 62120 0 master MERGED core: Cannot import KVM VMs as clone 2020-08-21 13:13:46 UTC
oVirt gerrit 62177 0 ovirt-engine-4.0 MERGED core: Cannot import KVM VMs as clone 2020-08-21 13:13:46 UTC

Internal Links: 1302427

Description Nisim Simsolo 2016-08-04 15:07:48 UTC 
Description of problem:
Tring to import VM as clone failed with the next engine.log error:
2016-08-04 18:02:14,499 ERROR [org.ovirt.engine.core.bll.exportimport.ImportVmFromExternalProviderCommand] (org.ovirt.thread.pool-6-thread-21) [366e749d] Command 'org.ovirt.engine.core.bll.exportimport.ImportVmFromExternalProviderCommand' failed: CallableStatementCallback; SQL [{call insertvmdevice(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}]; ERROR: insert or update on table "vm_device" violates foreign key constraint "fk_vm_device_vm_static"
  Detail: Key (vm_id)=(9af6f0e4-c1fd-487c-b4ca-f031e6d16495) is not present in table "vm_static".
  
Version-Release number of selected component (if applicable):
ovirt-engine-4.0.2.2-0.1.el7ev
vdsm-4.18.9-1.el7ev.x86_64
qemu-kvm-rhev-2.3.0-31.el7_2.20.x86_64
libvirt-client-1.2.17-13.el7_2.5.x86_64
sanlock-3.2.4-3.el7_2.x86_64

How reproducible:
Consistently

Steps to Reproduce:
1. Import VM as a clone from KVM environment.
2.
3.

Actual results:
Import failed.

Expected results:
Import should succeed.

Additional info:
engine and vdsm log attached.
Comment 1 Nisim Simsolo 2016-08-04 15:12:40 UTC 
Created attachment 1187563 [details]
engine.log.gz issue occured at: 2016-08-04 18:02:14,499
Comment 2 Nisim Simsolo 2016-08-04 15:13:03 UTC 
Created attachment 1187564 [details]
vdsm.log.gz
Comment 3 Nisim Simsolo 2016-09-01 14:39:02 UTC 
Verified:
ovirt-engine-4.0.4-0.1.el7ev
qemu-kvm-rhev-2.3.0-31.el7_2.21.x86_64
vdsm-4.18.12-1.el7ev.x86_64
libvirt-client-1.2.17-13.el7_2.5.x86_64
sanlock-3.2.4-3.el7_2.x86_64
Note You need to log in before you can comment on or make changes to this bug.