Bug 1383634 - RHEVM should clean iscsi session after removing direct LUN from VM.
Summary: RHEVM should clean iscsi session after removing direct LUN from VM.
Keywords:
Status: CLOSED DUPLICATE of bug 1146115
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.0.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-11 10:03 UTC by Ulhas Surse
Modified: 2019-12-16 07:07 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-12 15:03:12 UTC
oVirt Team: Storage
Target Upstream Version:


Attachments (Terms of Use)

Description Ulhas Surse 2016-10-11 10:03:27 UTC
3. What is the nature and description of the request?
   After removing the Direct LUN disk from VM permanently, the session for iscsi remains on the Host. It should be cleared so as to unmap LUN from storage end. 

4. Why does the customer need this? (List the business requirements here)
   To ease the use of LUN map and unmap. 

5. How would the customer like to achieve this? (List the functional requirements here)
   Clear the session of iscsi so as to unmap LUN from storage. 

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
   Yes

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
   No. There was one for storage domain #880738. 

8. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
    No

9. Is the sales team involved in this request and do they have any additional input?
   No

10. List any affected packages or components.
    RHEVM

11. Would the customer be able to assist in testing this functionality if implemented?
    Yes

Comment 5 Tal Nisan 2016-12-12 15:03:12 UTC

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


Note You need to log in before you can comment on or make changes to this bug.