Bug 1138121

Summary:	[RFE][ImportDomain] External LUN disk should be also discovered from the Lun
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Maor <mlipchuk>
Component:	ovirt-engine	Assignee:	Maor <mlipchuk>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	amureini, ecohen, gklein, iheim, lpeer, mlipchuk, rbalakri, Rhev-m-bugs, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	storage
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-22 12:21:13 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:

Description Maor 2014-09-04 06:28:35 UTC

Description of problem:
Import Storage Domain of block Device should also import Lun disks which reflected by the Luns without Storage Domain they are contained in them

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Try to import target of iSCSI domain
2.
3.

Actual results:
No Direct Lun will be found

Expected results:
Direct Lun should be presented when trying to discover the target they are based on, and should be registered as a disk when the user desires to

Additional info:

Comment 1 Allon Mureinik 2014-09-04 11:17:44 UTC

I do not understand this BZ.
You do NOT import a target - you import a domain, which should not be presented as a LUN.

Comment 2 Maor 2014-09-30 09:41:49 UTC

(In reply to Allon Mureinik from comment #1)
> I do not understand this BZ.
> You do NOT import a target - you import a domain, which should not be
> presented as a LUN.

As described in the expected result:
Direct Lun should be presented when trying to discover the target they are based on, and should be registered as a disk when the user desires to.

The steps to reproduce should be:
1. Try to connect to a target contains LUN disk
2.
3.

Comment 3 Allon Mureinik 2014-10-07 18:16:59 UTC

Again - any LUN is potentially a direct LUN.
How would you discover it? How would you distinguish it used to be a direct LUN?

Comment 4 Maor 2014-12-22 12:21:13 UTC

Referring to Allon's comments at https://bugzilla.redhat.com/show_bug.cgi?id=1138121#c3,
Since direct LUN is an entity which is mainly managed by the user, it is more appropriate that the user will manage direct Lun disks on a Disaster Recovery scenario by adding it directly to the setup as it is already done today when adding a Direct Lun disk.

The only "gap" which had to be considered was a VM which had only direct Lun disks, and this bug was already solved (https://bugzilla.redhat.com/1138134), so this bug might not be relevant any more.
Therefore closing it as Not a Bug