Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
After fcoe-target daemon stop, all fcoe-target session is still running.
/etc/init.d/fcoe-taget
====
112 stop()
113 {
114 echo "Stopping $prog: "
115
116 echo -n " Unloading $prog modules... "
117 stop_ccsd
118 if [ $? -eq 0 ]
119 then
120 >---echo "done"
121 else
122 >---echo "failed"
123 >---return 1
124
====
stop_ccsd() didn't exist. You must mean "unload_modules()" function.
Version-Release number of selected component (if applicable):
fcoe-target-utils-2.0rc1.fb10-4.el6.noarch
How reproducible:
100%
Steps to Reproduce:
1. Start FCoE target session.
2. Stop fcoe-target daemon.
3. Check wether fcoe-taget session got removed.
Actual results:
all target session still exist.
Expected results:
all target session got removed.
Additional info:
No sure whether change "stop_ccsd()" to "unload_modules()" fix the problem or not. Please be informed, this bug is aim to make sure all fcoe-target session got disabled when daemon stop.
BTW:
1. the format of /etc/target/saveconfig.json is not user-friently.
2. the way of targetcli force us to use "expect" or similar tool for scripting.
3. scsi-target-utils set a very good example for how a target severs should be.
Reopen,
Stop daemon still failed like these:
=====
[root@storageqe-14 ~]# /etc/init.d/fcoe-target stop
Deactivating FCoE Target... done
Unloading FCoE Target modules... failed
ERROR: Module target_core_mod is in use by tcm_fc
[FAILED]
=====
[root@storageqe-14 ~]# lsmod|grep fc
tcm_fc 27313 1
libfc 108727 1 tcm_fc
target_core_mod 343420 2 tcm_fc
scsi_transport_fc 55235 2 libfc,bfa
scsi_tgt 12173 1 scsi_transport_fc
=====
If I stop daemon again, I got this:
=====
[root@storageqe-14 ~]# /etc/init.d/fcoe-target stop
Deactivating FCoE Target... done
Unloading FCoE Target modules... failed
ERROR: Module target_core_pscsi does not exist in /proc/modules
[FAILED]
=====
Please use "modporbe -qra foo_a foo_b" instead of rmmod.
Decrease priority and request fix in RHEL 6.4 as QE resource limit.
If we found any other urgent bug for fcoe-target, we can treat this bug as exception.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0457.html
Description of problem: After fcoe-target daemon stop, all fcoe-target session is still running. /etc/init.d/fcoe-taget ==== 112 stop() 113 { 114 echo "Stopping $prog: " 115 116 echo -n " Unloading $prog modules... " 117 stop_ccsd 118 if [ $? -eq 0 ] 119 then 120 >---echo "done" 121 else 122 >---echo "failed" 123 >---return 1 124 ==== stop_ccsd() didn't exist. You must mean "unload_modules()" function. Version-Release number of selected component (if applicable): fcoe-target-utils-2.0rc1.fb10-4.el6.noarch How reproducible: 100% Steps to Reproduce: 1. Start FCoE target session. 2. Stop fcoe-target daemon. 3. Check wether fcoe-taget session got removed. Actual results: all target session still exist. Expected results: all target session got removed. Additional info: No sure whether change "stop_ccsd()" to "unload_modules()" fix the problem or not. Please be informed, this bug is aim to make sure all fcoe-target session got disabled when daemon stop. BTW: 1. the format of /etc/target/saveconfig.json is not user-friently. 2. the way of targetcli force us to use "expect" or similar tool for scripting. 3. scsi-target-utils set a very good example for how a target severs should be.