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

Bug 1360321

Summary: Importing a VM from 3.6 fails
Product: [oVirt] ovirt-engine Reporter: Petr Matyáš <pmatyas>
Component: Backup-Restore.VMsAssignee: bugs <bugs>
Status: CLOSED DUPLICATE QA Contact: bugs <bugs>
Severity: high Docs Contact: bugs <bugs>
Priority: unspecified    
Version: 4.0.2CC: bugs, michal.skrivanek
Target Milestone: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 05:06:19 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:
Attachments:
Description Flags
engine log none

Description Petr Matyáš 2016-07-26 12:27:32 UTC
Created attachment 1184247 [details]
engine log

Description of problem:
When I export a VM with some snapshots on NFS export domain on 3.6.8-4 and try to import it on 4.0.2-1, the import fails with ERROR [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (org.ovirt.thread.pool-6-thread-44) [46c81263] Exception: javax.ej
b.EJBTransactionRolledbackException: Coding error, pool for requested GUID does not exist
Although the VM was not in any pool and was created from template Blank

Version-Release number of selected component (if applicable):
RHV 3.6.8-4
RHV 4.0.2-1

How reproducible:
always

Steps to Reproduce:
1. export a vm with snapshots (don't collapse them) on 3.6 engine on nfs export domain
2. attach that domain to 4.0 engine
3. try to import the vm (either with or without collapsing snapshots)

Actual results:
fail

Expected results:
successful import

Additional info:

Comment 1 Michal Skrivanek 2016-07-27 05:06:19 UTC

*** This bug has been marked as a duplicate of bug 1359668 ***