Bug 184267 - /etc/init.d/iscsi reload does not remove old targets.
Summary: /etc/init.d/iscsi reload does not remove old targets.
Status: CLOSED DUPLICATE of bug 184262
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: iscsi-initiator-utils   
(Show other bugs)
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Tom Coughlan
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2006-03-07 19:07 UTC by Wayne Berthiaume
Modified: 2008-04-07 05:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-07 20:26:35 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Wayne Berthiaume 2006-03-07 19:07:03 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705; InfoPath.1)

Description of problem:
If you change the discovery addresses in the /etc/iscsi.conf file then perform an /etc/init.d/iscsi reload, the new target is loaded in; however, the old target that was removed from the configuration file remains.

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

How reproducible:

Steps to Reproduce:
1. Configure /etc/iscsi.conf with a set of targets
2. Start driver and insure all targets are discovered with iscsi-ls
3. Edit /etc/iscsi.conf and remove one target and add a new target
4. Execute /etc/init.d/iscsi reload
5. iscsi-ls

Actual Results:  The new target is discovered; however, the old target still remains when you issue the iscsi-ls() command.

Expected Results:  You would expect that after the rescan the old target would be removed and the new target added.

Additional info:

 SFNet iSCSI Driver Version ...4:0.1.11(12-Jan-2005)

Comment 1 David Lawrence 2006-03-07 20:26:35 UTC

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

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