Created attachment 1368045 [details] logs Description of problem: Registering VM with LUN exposed by FC fails with the following: 2017-12-14 16:30:29,483+02 WARN [org.ovirt.engine.core.bll.exportimport.ImportVmFromConfigurationCommand] (default task-5) [] Validation of action 'ImportVmFromConfiguration' failed for user admin@internal-authz. Reasons: VAR__ACTION__IMPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_DISK_LUN_HAS_NO_VALID_TYPE Version-Release number of selected component (if applicable): rhvm-4.2.0.2-0.1.el7.noarch vdsm-4.20.9.1-1.el7ev.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a VM with 1 image disk on FCP domain and one direct LUN that reside on that FCP domain 2. Maintenance and detach the FCP domain 3. Attach the FCP domain to the data center 4. Register the VM Actual results: VM registration is blocked while the VM has an FCP direct LUN written in its OVF Expected results: VM registration should succeed Additional info:
Elad, will it be possible to attach the VM's OVF. It should be in the DB: "SELECT entity_guid, entitY_name, ovf_data FROM unregistered_ovf_of_entities where entitY_name = 'NAME_OF_VM';"
Created attachment 1368640 [details] OVF
VM registration with direct LUN works as expected. Used rhvm-4.2.1-0.2.el7.noarch
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 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.