Project

General

Profile

Bug #25673

After adding new iscsi target, not visible for initiator until service restart

Added by Thomas Sjunnesson about 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
No priority
Assignee:
Alexander Motin
Category:
OS
Target version:
Seen in:
Severity:
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Setup iscsi-target 2TB-01, it became immediately visible for the iscsi initiator and it worked without any problems.
Added a couple more targets (2TB-02, 2TB-03, 2TB-04). Those targets did not become available to the initator until the iscsi service was stopped and started.
This would cause an interruption to the iscsi targets in use.

History

#1 Updated by Dru Lavigne about 3 years ago

  • Assignee changed from Release Council to Alexander Motin
  • Private changed from No to Yes

#2 Updated by Thomas Sjunnesson about 3 years ago

After upgrading to FreeNAS-11.0-U3 the phenomena disappeared.
Hence, someone may Close this case.

#3 Updated by Dru Lavigne about 3 years ago

  • File deleted (debug-klaus-20170824073549.tgz)

#4 Updated by Dru Lavigne about 3 years ago

  • Status changed from Unscreened to Closed: Not Applicable
  • Target version set to N/A
  • Private changed from Yes to No

#5 Avatar?id=14398&size=24x24 Updated by Kris Moore over 2 years ago

  • Status changed from Closed: Not Applicable to Closed

#6 Updated by Marco Saarloos over 2 years ago

  • Seen in changed from 11.0-U2 to 11.1-U4

I have this issue in 11.1-U4. Should I file a new bug report or not?

#7 Updated by Alexander Motin over 2 years ago

Generally I would say open a new one, unless you wish to share your data with the original reported. Also I would ask to provide debug information grabbed when the problem was experienced (targets created, but initiator(s) not seeing them).

Also available in: Atom PDF