| Summary: | RHEVM should clean iscsi session after removing direct LUN from VM. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Ulhas Surse <usurse> |
| Component: | ovirt-engine | Assignee: | Nobody <nobody> |
| Status: | CLOSED DUPLICATE | QA Contact: | Raz Tamir <ratamir> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0.3 | CC: | gklein, lsurette, michal.skrivanek, ratamir, rbalakri, Rhev-m-bugs, srevivo, tnisan, ykaul, ylavi |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-12 15:03:12 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: | |
*** This bug has been marked as a duplicate of bug 1146115 *** |
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