Ubuntu
open-iscsi package

iscsid is started before networking

Bug #1025240 reported by RoyK
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
open-iscsi (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have two servers hooked up to a SAN, and when attempting to connect to the shared LUN, at least one of them can't connect automatically, and comes up without /dev/sdb visible in /proc/partitions

[ 39.284628] Loading iSCSI transport class v2.0-870.
[ 39.288712] iscsi: registered transport (tcp)Jul 16 14:03:13 kvm-test2 kernel: [ 39.294101] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 39.310000] iscsi: registered transport (iser)
[ 39.312942] iscsid (905): /proc/905/oom_adj is deprecated, please use /proc/905/oom_score_adj instead.
[...]
[ 41.673758] tg3 0000:02:00.0: eth1: Link is up at 1000 Mbps, full duplex
[ 41.673761] tg3 0000:02:00.0: eth1: Flow control is off for TX and off for RX
[ 41.675092] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready

After bootup, "iscsiadm -m discovery" and "iscsiadm -m node" show correct info, and a subsequent "iscsiadm -m node -l" successfully connects to the LUN. However, this does not work automatically. I have set node.startup = automatic in /etc/iscsi/iscsid.conf and tries to increase node.conn[0].timeo.login_timeout from 15 to 60 without success. We only use the auto-generated initiator name as authentication, no chap or otherwise.

Any idea how to fix this?

roy

Revision history for this message
RoyK (roysk) wrote :

Please just close/ignore this one, or perhaps just change it to a documentation bug. Seems if node startup is set to manual in /etc/iscsi/iscsid.conf, this setting is copied to the target, so that even if the former is changed later, it isn't reflected in the already discovered target. Changing this manually, fixes the problem

roy

Revision history for this message
Ritesh Raj Sarraf (rrs) wrote : Re: [Bug 1025240] Re: iscsid is started before networking

On Monday 16 July 2012 06:02 PM, RoyK wrote:
> Please just close/ignore this one, or perhaps just change it to a
> documentation bug. Seems if node startup is set to manual in
> /etc/iscsi/iscsid.conf, this setting is copied to the target, so that
> even if the former is changed later, it isn't reflected in the already
> discovered target. Changing this manually, fixes the problem
 Yes. And not just the startup setting, but also all other settings.
These settings are read during discovery and accordingly the database is
created. Updation of the records for the discovered targets will
require the usage of 'iscsiadm -m node ' command.

--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in open-iscsi (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.