if-up.d/if-down.d scripts restart iSCSI inappropriately
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
open-iscsi (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: open-iscsi
When any interface that is not named "lo" is brought up or down, it will cause open-iscsi to restart. This is regardless of if the interface has anything to do with iSCSI traffic, which can cause problems for LUNs still in use.
The fragment of the script /etc/init.
# Support for ifupdown script.
# Don't bother to restart when lo is configured.
if [ "$IFACE" = lo ]; then
exit 0
fi
Restricting restarts purely for the loopback interface is not sufficient, although adequately determining if a restart is actually required may be somewhat tricky. Sadly I have no suggestions for a solution at the moment.
### System Information ###
Description: Ubuntu 10.04.1 LTS
Release: 10.04
open-iscsi 2.0.871-0ubuntu4
Changed in open-iscsi (Ubuntu): | |
status: | New → Confirmed |
tags: | added: canonistack |
I would recommend even fully skipping these scripts.
We have various machines running with KVM and multiple network interfaces. For example, when we want to bring down a bridge, Open-iSCSI stops, which causes all our Virtual Machines to crash:
ifdown vlanbr103
That will cause Open-iSCSI to stop, while there is no iSCSI traffic over that interface (it's bridge!).
I'd like to see this scripts removed from Open-iSCSI since they do more harm then good.