Red Hat Bugzilla – Bug 747479
iscsi targets starting before network is up for non-critical mounts on boot
Last modified: 2012-06-26 12:08:40 EDT
Description of problem:
I did a minimal install (no NM) for F16 i386 and added /opt as a 20G
When I boot, iscsi and iscsid attempt to start before networking is up
and the target is not mounted.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install F16 with an iSCSI target as /opt
/opt is not mounted on reboot because the network isn't up before the system tries to mount the iSCSI target
/opt is mounted at boot
The only way I've been able to get the iscsi target to mount @ boot is to change either the iscsid or iscsi init script to depend on $network.
Created attachment 529149 [details]
boot log excerpt showing iscsi starting before network and failing
Proposing as NTH for Fedora 16 final as it violates the following final release criterion :
The installer must be able to complete an installation using any network-attached storage devices (e.g. iSCSI, FCoE, Fibre Channel).
However, it only affects systems without NetworkManager and doesn't seem appropriate for a blocker.
This was accepted at the 2011-10-21 NTH review meeting but not updated, updating now.
I am seeing this same issue.
I was going to just merge a fix so that network is added to the RequiredStart section of the iscsi init script, but while testing this I noticed it does not help in F16 with the rpms all up to date (I thought this fixed the problem before).
In your setups, do you have network init script setup? Is it linked properly in /etc/rc*.d/ ? Does
chkconfig --list network
show it is setup properly?
If you run
chkconfig network on
does it then work? Is the problem that we want this to be done automatically?
Or in your setups is the network coming up after the iscsi script? If so, could you send the output of
ls -l /etc/rc5.d/*
(replace 5 with your value).
chkconfig --list network
Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
network 0:off 1:off 2:on 3:on 4:on 5:on 6:off
lrwxrwxrwx 1 root root 16 Dec 6 2009 /etc/rc5.d/S07iscsid -> ../init.d/iscsid
lrwxrwxrwx 1 root root 16 Jan 23 2010 /etc/rc5.d/S08nvidia -> ../init.d/nvidia
lrwxrwxrwx 1 root root 14 Sep 21 2010 /etc/rc5.d/S09capi -> ../init.d/capi
lrwxrwxrwx 1 root root 14 Sep 21 2010 /etc/rc5.d/S09isdn -> ../init.d/isdn
lrwxrwxrwx 1 root root 17 Nov 8 11:08 /etc/rc5.d/S10network -> ../init.d/network
lrwxrwxrwx 1 root root 15 Dec 20 16:17 /etc/rc5.d/S13iscsi -> ../init.d/iscsi
Ping, where are we on this? Any chance of a fix for F17?
Fedora Bugzappers volunteer triage team
I found the cause of the bug for me. I use network instead of network-manager, and /var/lock/subsys/network doesn't exist yet, even though the interfaces are up. When I comment out the check, it works.
# if the network isn't up yet exit cleanly, NetworkManager will call us
# again when the network is up
[ ! -f /var/lock/subsys/network ] && ! nm-online -x >/dev/null 2>&1 && exit 3
I just double checked things and found I am wrong on the details, but commenting out the line does fix it for me.
Here is the timing:
Feb 3 16:14:04 proton network: Bringing up loopback interface: [ OK ]
Feb 3 16:14:06 proton network: Bringing up interface eth0: [ OK ]
Feb 3 16:14:08 proton network: Bringing up interface eth1: [ OK ]
Feb 3 16:14:11 proton network: Bringing up interface eth2: [ OK ]
Feb 3 16:14:22 proton iscsi: Starting iscsi: [ OK ]
ls -al --time-style full-iso /var/lock/subsys/network
-rw-r--r-- 1 root root 0 2012-02-03 16:14:11.153393551 -0800 /var/lock/subsys/network
So /var/lock/subsys/network does get created right after eth2 comes up, and iscsi comes up 11 seconds later.
I also proved it isn't the line below during testing by changing the exit code for the network line from 3 to 4.
[ $? -eq 0 ] || exit 3
So it all comes down to the line below not working.
[ ! -f /var/lock/subsys/network ] && ! nm-online -x >/dev/null 2>&1 && exit
This should be fixed in
iscsi-initiator-utils-220.127.116.112-15.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing iscsi-initiator-utils-18.104.22.1682-15.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Works for me. Thank you!
iscsi-initiator-utils-22.214.171.1242-16.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.