It breaked my complex network initialisation at boot time (br+vlan+bond) until
I removed the symlink /etc/network/if-up.d/open-iscsi
I use ubuntu 12.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am not sure if my iscsi config is general for all ubuntus, but at
least I replaced
if [ $IFACE = lo ]; then
exit 0
fi
with
if iscsiadm -m iface --op=show | grep -q ,$(ip link show $IFACE
2/dev/null | awk '$1==link/ether {print $2}'), ; then
--
You received this bug notification
This affected me,
Today I was adding a new interface and when I ifdown it it stop iscsi
service which caused multipath to fail, and then LVM and a few KVM
guests, I think you should remove this script from if-down.d and if-up.d
because it causes more damages than it helps.
It happend in ubuntu
** Tags added: canonistack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669142
Title:
if-up.d/if-down.d scripts restart iSCSI inappropriately
To manage notifications about this bug go to:
Yes, still present in 12.04. This is a totally ridiculous mis-feature.
I'm having a hard time coming up with real scenarios in which you'd want
iscsid state to be changed when any single interface is brought down/up
(that is, outside of system init or shutdown).
--
You received this bug
Still present in 12.04. Glad I found it before putting very much on
there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669142
Title:
if-up.d/if-down.d scripts restart iSCSI inappropriately
To
Seeing the same in Maverick and Oneiric. Killed our VM-platform.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669142
Title:
if-up.d/if-down.d scripts restart iSCSI inappropriately
To manage
I experienced the same issue.
I've modified the beginning of the script this way :
PATH=/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/sbin/iscsid
ADM=/sbin/iscsiadm
PIDFILE=/var/run/iscsid.pid
NAMEFILE=/etc/iscsi/initiatorname.iscsi
ISCSI_INTERFACE=br1:0
[ -x $DAEMON ] || exit 0
# Support for
Actually, I've slighly updated it :
# Support for ifupdown script.
# Don't bother to restart when lo is configured.
if [ $IFACE != $ISCSI_INTERFACE ] [ -n $IFACE ]; then
echo Not restarting ISCSI daemon... (check the value of
ISCSI_INTERFACE)
exit 0
fi
Which means that I
** Changed in: open-iscsi (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/669142
Title:
if-up.d/if-down.d scripts restart iSCSI inappropriately
To manage
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
11 matches
Mail list logo
