As a temporary workaround for beta2, I'd recommend we update the open-iscsi
script to:
- Check if /etc/iscsi/iscsi.initramfs exists
- If it does, then check if iscsiadm -m session reports any established
session
- If it does, then exit 0
This will restore the old behaviour we had before the
** Package changed: Ubuntu Oneiric = open-iscsi (Ubuntu Oneiric)
** Changed in: open-iscsi (Ubuntu Oneiric)
Milestone: ubuntu-11.10-beta-2 = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package open-iscsi - 2.0.871-0ubuntu8
---
open-iscsi (2.0.871-0ubuntu8) oneiric; urgency=low
* Disable open-iscsi init script when root is on iscsi (LP: #838809)
-- Stephane Graber stgra...@ubuntu.com Thu, 15 Sep 2011 10:01:12 -0400
** Changed in:
When was the last time that test was successful?
I had a quick look through the package history and can't find anything
in open-iscsi that'd explain this bug (package almost didn't change
since natty) and my VM now runs Natty's kernel and still reproduces the
bug.
--
You received this bug
Stephane
These tests passed during alpha3 testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838809
Title:
authenticated and unauthenicated iscsi clients fails to complete boot
To manage
The change that is causing this issue to occur is in upstart:
http://launchpadlibrarian.net/76962956/upstart_1.3-0ubuntu5_1.3-0ubuntu6.diff.gz
If I revert the change to rc-sysinit.conf the system boots fine - open-
iscsi is only run on IFACE lo which does an exit 0 so no iscsid is
tarted.
With
so the problem is that the init script now does what it's supposed to
do.
I did a quick test on Natty and can also confirm that back then iscsid
was just exitting and never tried to setup iscsi at boot time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Starting iscsid manually (which seems to be the part of open-iscsi that breaks
the system) gives me:
iscsid: Login failed to authenticate with target
iqn.2010-01.com.example:storage.lun1
iscsid: session 1 login rejected: Initiator failed authentication with target
Then everything freezes and I
I guess I'll need to talk to someone with a bit more iscsi experience
though my feeling so far is that iscsistart works properly from the
initramfs, mounts the lun and then mounts the root device.
When iscsid then starts, it tries to disconnect the existing device and
re-establish the connection
Digging a little deeper, here's the dump of a connection on the server when
done from initramfs:
Sep 9 16:33:47 ubuntu ietd: 49 6e 69 74 | 69 61 74 6f | 72 4e 61 6d | 65 3d
69 71 | InitiatorName=iq |
Sep 9 16:33:47 ubuntu ietd: 6e 2e 31 39 | 39 33 2d 30 | 38 2e 6f 72 | 67 2e
64 65 |
Here is the result of a grep -i auth on the level 9 debug output of
iscsid on the client.
iscsid: updated 'node.session.auth.authmethod', 'None' = 'None'
iscsid: updated 'node.session.auth.authmethod', 'None' = 'None'
iscsid: updated 'node.conn[0].timeo.auth_timeout', '45' = '45'
iscsid: updated
Successfully reproduced here on kvm.
Initial testing shows that the open-iscsi init script seems to be the cause of
the disconnect and input/output errors.
Removing it from the boot sequence lets me boot and get a shell without storage
related errors.
I'm not too familiar with iscsi so I'll
This appears to be reproducible on arm platforms as well, using both
AMD64 and armel target hosts and armel initiator.
As to documentation, we need better documentation for raw system setup.
Not everyone will be running this in a vm (actually, quite few I would
imagine).
** Attachment added:
** Changed in: ubuntu
Milestone: None = ubuntu-11.10-beta-2
** Tags removed: server-o-rs
** Tags added: server-o-ro
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838809
Title:
authenticated
** Also affects: Ubuntu Oneiric
Importance: Undecided
Status: New
** Changed in: Ubuntu Oneiric
Importance: Undecided = High
** Changed in: Ubuntu Oneiric
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Assigning to canonical-foundations, if that's wrong punt it back to the
ubuntu-server team. -Robbie
** Changed in: Ubuntu Oneiric
Assignee: (unassigned) = Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: Ubuntu Oneiric
Assignee: Canonical Foundations Team (canonical-foundations) = Stéphane
Graber (stgraber)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838809
Title:
Hello!
So I'm expecting to have some time to look at that bug next week. I just
had a quick look at how to get a setup in place to reproduce the bug and
found the instructions for the ISO testing at:
http://testcases.qa.ubuntu.com/Install/ServeriSCSIRoot
Which describe who to get the client VM
** Attachment added: amd64-auth.png
https://bugs.launchpad.net/ubuntu/+bug/838809/+attachment/2339911/+files/amd64-auth.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838809
Title:
** Attachment added: amd64-auth-errors.png
https://bugs.launchpad.net/ubuntu/+bug/838809/+attachment/2339912/+files/amd64-auth-errors.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838809
I can of course mount the target disks on the iscsi target host itself
if anything on the target filesystem might be of interest.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838809
Title:
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838809
Title:
authenticated and unauthenicated iscsi clients fails to complete boot
To manage notifications about this bug
I wonder if this is another case of networking being ripped out from
under the iSCSI stack during boot? That's been a problem in the past.
The best way to debug this is usually to boot with init=/bin/sh and then
manually bring up the system, running steps from Upstart jobs by hand.
It's tedious
** Tags added: server-o-rs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/838809
Title:
authenticated and unauthenicated iscsi clients fails to complete boot
To manage notifications about this bug
24 matches
Mail list logo
