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

Bug 1525989

Summary: Cannot register VM with FC LUN
Product: [oVirt] ovirt-engine Reporter: Elad <ebenahar>
Component: BLL.StorageAssignee: Maor <mlipchuk>
Status: CLOSED CURRENTRELEASE QA Contact: Elad <ebenahar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, ebenahar
Target Milestone: ovirt-4.2.1Flags: rule-engine: ovirt-4.2+
rule-engine: blocker+
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-12 11:56:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1477505    
Attachments:
Description Flags
logs
none
OVF none

Description Elad 2017-12-14 14:40:12 UTC
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:

Comment 1 Maor 2017-12-15 01:20:42 UTC
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';"

Comment 2 Elad 2017-12-15 19:23:50 UTC
Created attachment 1368640 [details]
OVF

Comment 3 Elad 2018-01-07 11:47:15 UTC
VM registration with direct LUN works as expected.

Used 
rhvm-4.2.1-0.2.el7.noarch

Comment 4 Sandro Bonazzola 2018-02-12 11:56:38 UTC
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.