Bug 789683 - iscsi init script blocks boot-process for minutes
Summary: iscsi init script blocks boot-process for minutes
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: iscsi-initiator-utils
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Chris Leech
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-12 11:27 UTC by Clemens Eisserer
Modified: 2014-09-13 18:59 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-14 03:05:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Clemens Eisserer 2012-02-12 11:27:34 UTC
Description of problem:

After updating Fedora16 to the latest available packages, I found that the iscsi init scripts where blocking the book-process of my notebook by several minutes. Unfourtunatly even updating to updates-testing didn't help.

According to systemd developers this is caused by broken iscsi init scripts that cause systemd to stall during boot until it hits a timeout, see bug 787366 for more details.


In /var/log/boot.log I found the following entry: 

Failed to start LSB: Starts and stops login and scanning of iSCSI
devices.
             [FAILED]
See 'systemctl status iscsi.service' for details.


Quering the status of iscsi however tells me everything went fine:

$ systemctl status iscsi.service
iscsi.service - LSB: Starts and stops login and scanning of iSCSI devices.
         Loaded: loaded (/etc/rc.d/init.d/iscsi)
         Active: active (exited) since Sat, 11 Feb 2012 23:17:58 +0100; 18s ago
        Process: 1731 ExecStart=/etc/rc.d/init.d/iscsi start (code=exited,
status=0/SUCCESS)
         CGroup: name=systemd:/system/iscsi.service


Version-Release number of selected component (if applicable):
systemd-37-13.fc16.i686
iscsi-initiator-utils-6.2.0.872-16.fc16.i686


How reproducible:
Every boot

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Mike Christie 2012-02-14 01:14:51 UTC
The problem is the iscsi script is waiting for the network to come up.

Are you using iscsi? If not then just chkconfig it off

chkconfig --del iscsi

If you are using some virt stuff that is using iscsi then I am working on it. Will try to have something tomorrow. If you get really desperate in the meantime and are not using iscsi you can remove the line:


    [ ! -f /var/lock/subsys/network ] && ! nm-online -t 60 >/dev/null 2>&1 && exit 3

from /etc/init.d/iscsi

Comment 2 Fedora Update System 2012-02-14 07:52:30 UTC
iscsi-initiator-utils-6.2.0.872-17.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/iscsi-initiator-utils-6.2.0.872-17.fc16

Comment 3 Clemens Eisserer 2012-02-14 08:17:04 UTC
Hi Mike,

I don't use iSCSI and have already disabled it, but it was enabled by default and might bother other users in the same situation.

Thanks, Clemens

Comment 4 Fedora Update System 2012-02-15 11:35:27 UTC
Package iscsi-initiator-utils-6.2.0.872-17.fc16:
* 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-6.2.0.872-17.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-1695/iscsi-initiator-utils-6.2.0.872-17.fc16
then log in and leave karma (feedback).

Comment 5 Marcel Poul 2012-02-25 13:40:59 UTC
Had the same problem as Clemens.
Update to iscsi-initiator-utils-6.2.0.872-17.fc16 seems solved time-out issue.

Entry in /var/log/boot.log remains: 

Failed to start LSB: Starts and stops login and scanning of iSCSI
devices.
             [FAILED]
See 'systemctl status iscsi.service' for details.

But I think I don't need that service and can turn it off.

Comment 6 Tom Repetti 2012-03-04 01:46:55 UTC
Disabling the service is probably the best route. I am not sure why it is defaulted as being on. It was an interesting move to enable iSCSI in the install process, but it might be overkill to leave it enabled by default after the user has chosen another target for the partition/install.

Comment 7 Mike Christie 2012-03-05 20:40:57 UTC
Are the people that are having this defaulted to on using any sort of virt tools?

By default iscsi should not get installed.

It is getting installed through a dependency with some virt stuff. The virt storage stuff wants iscsi installed and on in case usrs want to use it. We are working on making it more dynamic to avoid this issue.

If you are not using virt, and are getting iscsi installed without choosing it let me know. This should not be happening.

Comment 8 Tom Repetti 2012-03-06 12:23:03 UTC
Right you are. It is (in my case) a VirtualBox dependency. The issue is on the VMware end it seems. Thank you for the clarification!

Comment 9 Clemens Eisserer 2012-03-06 13:12:09 UTC
In my case the system was updated from Fedora-15 to Fedora-16, and I had installed both VMWare and VirtualBox.

However, the problem reported - iscsi causing boot delay - was introduced about two months ago with an online-update.

Comment 10 Tom Repetti 2012-03-07 20:47:36 UTC
After the 3.2.9 update today, iscsi and iscsid were re-enabled automatically and I had to disable them again. It might be something about the kernel update packaging that defaults them on.

Comment 11 Mike Christie 2012-03-07 23:30:40 UTC
(In reply to comment #10)
> After the 3.2.9 update today, iscsi and iscsid were re-enabled automatically
> and I had to disable them again. It might be something about the kernel update
> packaging that defaults them on.

The iscsi .spec file is doing this. I will fix it up.

Comment 12 Clemens Eisserer 2012-05-27 08:07:01 UTC
Still happens with stock Fedora-16-XFCE i686 livecd installation which has been updated with the latest stable updates.

Comment 13 Ladislav Nesnera 2012-05-31 16:55:09 UTC
I have got the same problem with updated Linux nb 3.3.7-1.fc16.x86_64 #1 SMP Tue May 22 13:59:39 UTC 2012 (LXDE) :(

Comment 14 Ladislav Nesnera 2012-05-31 17:02:04 UTC
and VirtualBox 4.1.16

Comment 15 Mike Christie 2012-05-31 20:53:15 UTC
Clemens and Ladislav,

Which issue are you guys commenting about?

1. The boot slow down? This should be fixed in iscsi-initiator-utils-6.2.0.872-17.fc16.

2. The issue where iscsi-initiator-utils renables itself to run at boot by default? This is not fixed yet.

Comment 16 hcgpalm 2012-09-29 19:27:50 UTC
The update seems to work perfectly for me. So what's holding it back from release? It's been in testing for more than 6 months now.

Comment 17 Fedora End Of Life 2013-01-17 02:04:30 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 18 Martin 2013-01-17 09:15:15 UTC
Mike, why is this update still in updates-testing? Could you push it into updates?
https://admin.fedoraproject.org/updates/FEDORA-2012-1695/iscsi-initiator-utils-6.2.0.872-17.fc16

Comment 19 Fedora End Of Life 2013-02-14 03:05:07 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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