This bug was fixed in the package open-iscsi - 2.0.865-1ubuntu3.1
---
open-iscsi (2.0.865-1ubuntu3.1) hardy-proposed; urgency=low
* Backport changes from jaunty to allow iscsi targets to be activated
as network interfaces come on-line:
- debian/open-iscsi.init:
+ Support
** Branch linked: lp:ubuntu/hardy-proposed/open-iscsi
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
** Branch linked: lp:ubuntu/karmic/open-iscsi
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
** Tags added: verification-done
** Tags removed: verification-needed
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
Quick test lead me to believe that open-iscsi 2.0.865-1ubuntu3.1 from
hardy-proposed work as explained by Steve. That is, the block device
appear after the bonded Ethernet is brought up. It is too late for the
file system on the iSCSI target to be mounted from /etc/fstab, but at
least we do not h
Chris Puttick wrote:
> Consider me confused on the basis of my earlier comment showing how to
> configure Hardy so that iscsi volume mounts works consistently. It
> ain't broke, why fix it?
That is because you are not accessing the iSCSI target through a bonded
Ethernet interface. With plain Ethe
Accepted open-iscsi into hardy-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: open-iscsi (Ubuntu Har
Consider me confused on the basis of my earlier comment showing how to
configure Hardy so that iscsi volume mounts works consistently. It
ain't broke, why fix it?
--
My employers website: http://thehumanjourney.net - opinions in this
email are however very much my own and may not reflect that of
I've uploaded a backported fix for the open-iscsi part of this to hardy-
proposed, waiting now for review.
** Changed in: open-iscsi (Ubuntu Hardy)
Status: Confirmed => In Progress
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification beca
The biggest blocker for getting this fixed in hardy isn't bug #44194,
but rather Debian bug #383073 and Debian bug #383123 that were fixed in
a post-hardy merge of sysvinit. Without that fix, there's no way to
trigger mounting iscsi devices after they've been made available, which
is the problem t
** Changed in: open-iscsi (Ubuntu Intrepid)
Status: In Progress => Won't Fix
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Note: Hardy 8.04.2 2.6.24-18-virtual #1 SMP (running on KVM virtual
machine with dual guest CPU)
/etc/network/interfaces (relevant part)
auto eth1
iface eth1 inet static
address 192.168.20.50
netmask 255.255.255.224
ISCSI auto connect and mount works with no modifications using
I wouldn't recommend including this in Hardy, since it's known to break
wpasupplicant (see bug 44194) and we haven't even sorted that out in
Jaunty yet.
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification because you are a member of Ubuntu
Bugs,
Is this going to be fixed in Hardy as well? Thanks in advance.
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: open-iscsi (Ubuntu Hardy)
Assignee: Mathias Gug (mathiaz) => (unassigned)
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Changed in: open-iscsi (Ubuntu Hardy)
Assignee: (unassigned) => Mathias Gug (mathiaz)
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Changed in: open-iscsi (Ubuntu Hardy)
Importance: Undecided => High
Status: New => Confirmed
Target: None => ubuntu-8.04.3
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package open-iscsi - 2.0.870.1-0ubuntu1
---
open-iscsi (2.0.870.1-0ubuntu1) jaunty; urgency=low
* New upstream release:
- Support 2.6.26/27 kernels (LP: #289470).
- Fix iscsid shutdown (LP: #181188).
* Merge from Debian. Remaining Ubuntu changes:
Thanks, Dustin; I've included this text in the release notes, along with
a link to this bug.
** Changed in: ubuntu-release-notes
Assignee: (unassigned) => Colin Watson (kamion)
Status: New => Fix Released
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You receiv
Suggestion of text for the Intrepid release note (from Etienne Goyer):
File systems hosted on iSCSI targets may not be mounted automatically at
boot time, even if they have an entry in /etc/fstab, if a bridged or
bonded Ethernet interface is required to reach the iSCSI target. As a
work-around, y
I'm lowering this bug from Critical to High, and un-milestoning it for
Intrepid release.
We're not going to be able to fix this comprehensively, and in a way
that does not introduce regressions in time for Intrepid. Rather, I
will prepare some text for the Intrepid release notes, helping awarenes
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
I forgot to mention that the bit of code to add to open-iscsi init
script is from the Debian open-iscsi 2.0.869 package in unstable. So,
we will get it for jaunty in the next sync anyway.
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification beca
Dustin and myself worked on the bug today. We where able to fix the bug
with the following changes:
1. Add the _netdev option to filesystem on iscsi target in /etc/fstab.
We cannot do that retroactively for people who already have entries for
file system on iscsi target in fstab, so this will nee
That's still too late for local iscsi filesystems.
:-Dustin
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
The patch sent by Dustin already changes the open-iscsi script from S25
to S47, and (as we saw here) it seems that this is enough to mount any
storage volume after the network is up.
However, the original open-iscsi script position (S25) is before S45
(waitnfs) and S46 (mountnfs-bootclean), and in
** Changed in: open-iscsi (Ubuntu)
Importance: Undecided => Critical
Target: None => ubuntu-8.10
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Debian have fixed two related bugs:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423851
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438542
The solution might be to sync from Debian. Package 2.0.869~rc4-1 is supposed
to include modification to the init script that would fix this proble
The above solution is not entirely right, as the open-iscsi init script
will be run after /etc/rcS.d/mountall.sh, which mean that filesystem in
/etc/fstab that reside on iSCSI will not be available when mountall.sh
is ran.
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You r
** Changed in: open-iscsi (Ubuntu)
Status: Incomplete => In Progress
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Patch attached.
:-Dustin
** Attachment added: "open-iscsi.227848.debdiff"
http://launchpadlibrarian.net/18342692/open-iscsi.227848.debdiff
--
boot order wrong for iscsi
https://bugs.launchpad.net/bugs/227848
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I did the same as Christian Roessner, above: moved the open-iscsi link
from S25 to S42 in rcS.d. This is the preferred method, as - he also
pointed out - change the network order it's NOT a good idea.
Also, like Etienne Goyer stated, if you are using an "ordinary"
interface (ethX), udev may load t
I also have seen the wron startup ordering. But I only have moved the
open-iscsi from S25 to S47 in rcS.d. It must start _after_ networking
and not before. Changing network-ordering seems not to be a good idea
IMHO.
Everything is working with this simple change.
--
boot order wrong for iscsi
htt
I have a fairly consistent boot process now that mounts iSCSI drives. Here are
the changes I made to the default init scripts symlinks order:
rc0.d : changed K25open-iscsi to K44open-icsi
rc6.d: changed K25open-iscsi to K44open-iscsi
rcS.d: Changed S40networking to S23networking
in /etc/init.d, I
Having similar major problems utilizing iSCSI effectively with Heron. I have
changed the Boot script order in rcS.d so iSCSI is now S44 instead of S25 (
starts iscsi AFTER networking ) and I now have iSCSI drives available to the
system. However, it's proving difficult to get the boot order righ
The problem, I believe, come from the fact that open-iscsi is brought up
(S25 in /etc/rcS.d) before networking (S40 in /etc/rcS.d).
It is my understanding that udev bring interfaces up as they are
discovered, which mean that "bare" interfaces (eth0, eth1, etc) happen
to be brought up before /etc/r
36 matches
Mail list logo
