Bug 187408

Summary: scsi_transport_iscsi should have been rmmod after iscsi service stopped
Product: Red Hat Enterprise Linux 4 Reporter: issac <issacworld>
Component: iscsi-initiator-utilsAssignee: Mike Christie <mchristi>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 16:02:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description issac 2006-03-30 19:23:07 UTC
Description of problem:


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

[root@Y80 download]# uname -a
Linux Y80 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:54:53 EST 2006 i686 i686 i386
GNU/Linux
[root@Y80 download]# cat /etc/redhat-release 
Red Hat Enterprise Linux AS release 4 (Nahant Update 3)

How reproducible:
yes, every time

Steps to Reproduce:

[root@Y80 download]# service iscsi status
iSCSI driver is loaded

[root@Y80 download]# lsmod | grep iscsi
iscsi_sfnet            84240  2 
scsi_mod              116941  3 iscsi_sfnet,sg,sd_mod
scsi_transport_iscsi    12353  1 iscsi_sfnet

[root@Y80 download]# service iscsi stop
Stopping iSCSI: sync umount sync iscsid

[root@Y80 download]# lsmod | grep iscsi
scsi_transport_iscsi    12353  0       <------- note this should have been rmmod



  
Actual results:


Expected results:

"scsi_transport_iscsi" should have been removed after "iscsi service stopped"



Additional info:

Comment 1 Jiri Pallich 2012-06-20 16:02:09 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.