+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1451112 +++ ====================================================================== Description of problem: - Setup localfs domain in 3.6 - Create a disk and virtual machine with the disk - Install OS in the guest In the RHVM 4.1.2 - Setup initial localfs domain - Try to import the pre-configure domain from 3.6 It will show error: "Error while executing action Attach Storage Domain: Internal Engine Error" No such error in 4.0: From: rhevh-7.3-20170425.0.el6ev.iso (RHEVM Version: 3.6.11-0.1.el6) To: redhat-virtualization-host-4.0-20170307.0 (RHVM Version: 4.0.7.4-0.1.el7ev) Error showing 4.1.2: From: rhevh-7.3-20170425.0.el6ev.iso (RHEVM Version: 3.6.11-0.1.el6) To: redhat-virtualization-host-4.1-20170512.0 (RHVM Version: 4.1.2.2-0.1.el7) (Originally by dougsland)
Created attachment 1279104 [details] engine.log (Originally by dougsland)
Created attachment 1279356 [details] vdsm.log (Originally by dougsland)
Also encountered this issue with shared storage(FC). Error showing 4.1.2: From: rhevh-7.3-20170425.0.el6ev.iso (RHEVM Version: 3.6.11-0.1.el6) To: redhat-virtualization-host-4.1-20170518.0 (RHVM Version: 4.1.2.2-0.1.el7) (Originally by Huijuan Zhao)
Maor - given that BZ1446878 is MODIFIED, is there anything else to do here, or is it just another instance of the same issue? (Originally by Allon Mureinik)
Yes, it should be the same issue based on the postgres version mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1451112#c9 Moving to modify (Originally by Maor Lipchuk)
Verified with the following code: ---------------------------------------- ovirt-engine-4.1.3-0.1.el7.noarch rhevm-4.1.3-0.1.el7.noarch vdsm-4.19.16-1.el7ev.x86_64 Description of problem: - Setup localfs domain in 3.6 - Create a disk and virtual machine with the disk - Install OS in the guest In the RHVM 4.1.2 - Setup initial localfs domain - Try to import the pre-configure domain from 3.6 >>>>> Works fine Moving to VERIFIED!
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/RHEA-2017:1692