bad rc0 and rc6 script order for open-iscsi

Bug #597313 reported by marcus905
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
open-iscsi (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: open-iscsi

The order of the shutdown script in Ubuntu Server 10.04 is wrong for runlevel 0 and runlevel 6, as S35networking, the script that deconfigures network, is called before S40umountfs and S41open-iscsi, halting the shutdown/reboot process with a console message saying that iscsi lost a target for timeout therefore risking loss of data as the network connection terminates abruptly.

To fix that I renamed S35networking to S42networking, but I think that doing the reverse (that is: S40umountfs -> S33umountfs && S41open-iscsi -> S34open-iscsi) would work the same way.

In doing this fix I had no adverse effects to date.

lsb_release -rd:
Description: Ubuntu 10.04 LTS
Release: 10.04

apt-cache policy open-iscsi:
open-iscsi:
  Installed: 2.0.871-0ubuntu4
  Candidate: 2.0.871-0ubuntu4
  Version table:
 *** 2.0.871-0ubuntu4 0
        500 http://it.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

marcus905 (marcus90)
summary: - bad rc0 script order in open-iscsi
+ bad rc0 and rc6 script order for open-iscsi
Revision history for this message
Matt Chan (talcite-gmail) wrote :

Yep, I got bitten by this bug as well. It's actually quite devastating if you're working remotely and don't have access to a remote management console (which I was lucky enough to have).

Can we try and get a fix pushed out as soon as possible please? It's an extremely easy issue to resolve I think.

Matt

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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