Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1517793 - Cannot import Template. The snapshot configuration is corrupted (snapshot ID is empty)
Summary: Cannot import Template. The snapshot configuration is corrupted (snapshot ID ...
Status: NEW
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
medium vote
Target Milestone: ovirt-4.4.0
: ---
Assignee: Eyal Shenitzky
QA Contact: meital avital
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-27 13:31 UTC by Israel Pinto
Modified: 2019-01-04 02:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
oVirt Team: Virt
rbarry: ovirt-4.4?
ipinto: planning_ack?
ipinto: devel_ack?
ipinto: testing_ack?

Attachments (Terms of Use)
screenshot import failed message (deleted)
2017-11-27 13:32 UTC, Israel Pinto
no flags Details
spm_host_vdsm_log (deleted)
2017-11-27 13:33 UTC, Israel Pinto
no flags Details
engine_log (deleted)
2017-11-27 13:33 UTC, Israel Pinto
no flags Details
host_1_vdsm_log (deleted)
2017-11-27 13:34 UTC, Israel Pinto
no flags Details
host_2_vdsm_log (deleted)
2017-11-27 13:35 UTC, Israel Pinto
no flags Details

Description Israel Pinto 2017-11-27 13:31:31 UTC
Description of problem:
Failed to import template from 3.5 to 4.2.
(verifing BZ:

Version-Release number of selected component (if applicable):
Software version:4.2.0-0.5.master.el7

Steps to Reproduce:
In RHV 3.5: 
1. Import image from glance as template
2. Export template to export domain
3. Detached export domain 
In RHV 4.2
1. Attached export domain
2. Import template

Actual results:
Failed to import template, error message:
"Cannot import Template. The snapshot configuration is corrupted (snapshot ID is empty)"
See screenshot.

Expected results:
Template should be imported to RHV 4.2 with no error.

Additional info:
Engine log:
2017-11-27 11:23:26,129+02 WARN  [org.ovirt.engine.core.bll.exportimport.ImportVmTemplateCommand] (default task-32) [cf6ac9cc-45e1-4500-a763-43396dd8ae24] Validation of action 'ImportVmTemplate' failed for user admin@internal-authz. Reasons: VAR__ACTION__IMPORT,VAR__TYPE__VM_TEMPLATE,ACTION_TYPE_FAILED_CORRUPTED_VM_SNAPSHOT_ID
2017-11-27 11:23:26,402+02 INFO  [org.ovirt.engine.core.vdsbroker.irsbroker.GetVmsInfoVDSCommand] (default task-6) [ace6a2b9-9120-4937-b041-5597d2f5da0e] START, GetVmsInfoVDSCommand( GetVmsInfoVDSCommandParameters:{storagePoolId='c0819dcf-7b31-42d2-9d27-c5120db5938f', ignoreFailoverLimit='false', storageDomainId='e965911a-618e-4f42-8aa3-b92f565754e7', vmIdList='null'}), log id: 74dcae9e
2017-11-27 11:23:26,415+02 INFO  [org.ovirt.engine.core.vdsbroker.irsbroker.GetVmsInfoVDSCommand] (default task-6) [ace6a2b9-9120-4937-b041-5597d2f5da0e] FINISH, GetVmsInfoVDSCommand, log id: 74dcae9e

Attaching  logs

Comment 1 Israel Pinto 2017-11-27 13:32:36 UTC
Created attachment 1359459 [details]
screenshot import failed message

Comment 2 Israel Pinto 2017-11-27 13:33:22 UTC
Created attachment 1359460 [details]

Comment 3 Israel Pinto 2017-11-27 13:33:55 UTC
Created attachment 1359461 [details]

Comment 4 Israel Pinto 2017-11-27 13:34:29 UTC
Created attachment 1359463 [details]

Comment 5 Israel Pinto 2017-11-27 13:35:02 UTC
Created attachment 1359465 [details]

Comment 6 Michal Skrivanek 2017-11-27 14:58:18 UTC
4.2 doesn't support 3.5.

Comment 7 Israel Pinto 2017-11-27 15:07:05 UTC
(In reply to Michal Skrivanek from comment #6)
> 4.2 doesn't support 3.5.

No correct 
I just verify the BZ:
with template create in 3.5 and imported to 4.2.

The case here is the image is not created from VM, it was imported from glance.

Comment 8 Michal Skrivanek 2017-11-27 16:25:42 UTC
ok, that's what's different. It's possible the glance import is not correct (Tal, FYI)

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