I was able to install the Jaunty deb perfectly in my Intrepid system.
--
open-iscsi user-space does not match kernel module version
https://bugs.launchpad.net/bugs/289470
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-iscsi in
** Branch linked: lp:ubuntu/karmic/open-iscsi
--
open-iscsi user-space does not match kernel module version
https://bugs.launchpad.net/bugs/289470
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-iscsi in ubuntu.
--
I too have run into this issue, and wonder if an intrepid backport will
be ready soon.
--
open-iscsi user-space does not match kernel module version
https://bugs.launchpad.net/bugs/289470
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Any time line for of getting this package for jaunty working under
intrepid?
--
open-iscsi user-space does not match kernel module version
https://bugs.launchpad.net/bugs/289470
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-iscsi
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:
Any update on when we'll see an updated package for this issue?
--
open-iscsi user-space does not match kernel module version
https://bugs.launchpad.net/bugs/289470
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-iscsi in ubuntu.
--
On Tue, Nov 25, 2008 at 2:27 PM, Graeme Humphries [EMAIL PROTECTED] wrote:
Any update on when we'll see an updated package for this issue?
We're currently working on getting a working, merged package for Jaunty.
As soon as we finish that, we can begin the process for extracting the
bits we need
Updated Intrepid release notes with text above.
--
open-iscsi user-space does not match kernel module version
https://bugs.launchpad.net/bugs/289470
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-iscsi in ubuntu.
--
** Changed in: ubuntu-release-notes
Assignee: (unassigned) = Robbie Williamson (robbie.w)
Status: New = Fix Released
--
open-iscsi user-space does not match kernel module version
https://bugs.launchpad.net/bugs/289470
You received this bug notification because you are a member of
Draft for the release notes section:
Mounting multiple iscsi targets at the same time is currently not
supported. Systems configured to use more than one iscsi targets should
not be upgraded to Intrepid.
--
open-iscsi user-space does not match kernel module version
** Changed in: open-iscsi (Ubuntu)
Importance: Undecided = Critical
Assignee: (unassigned) = Dustin Kirkland (kirkland)
Status: New = Triaged
--
open-iscsi user-space does not match kernel module version
https://bugs.launchpad.net/bugs/289470
You received this bug notification
Dropping the importance. The option to display all active sessions and
connections doesn't work but open-iscsi is working in intrepid (iscsi
block devices can be created, mounted and files created on the
initiator). Not release critical.
Seems like a good candidate for a SRU.
** Changed in:
My observation is, that iscsi is working as long as I have only one
session to one target. But as soon as I have multiple sessions, iscsid
will overwrite my first session, bringing down all iscsi sessions. This
is due to the same reasons iscsiadm is not able to list all my sessions.
Only
The diffstat between 865 and the 870~rc3 (in debian) is quit large:
.gitignore|1
Changelog | 12
Makefile | 24
README| 280 +++-
debian/README.Debian
** Changed in: open-iscsi (Ubuntu Intrepid)
Importance: High = Critical
Status: Triaged = Confirmed
Target: intrepid-updates = ubuntu-8.10
--
open-iscsi user-space does not match kernel module version
https://bugs.launchpad.net/bugs/289470
You received this bug notification
Using 2.0.870~rc3-0.2, I was able to get the block devices working
correctly.
However iscsiadm -m session still fails:
[EMAIL PROTECTED]:~$ sudo iscsiadm -m session
iscsiadm: Could not get host for sid 1.
iscsiadm: could not get host_no for session 6.
iscsiadm: could not find session info for
Mathias, et al-
I've spent the entire day on this issue.
As Thierry has identified, most of Debian's diff.gz is undoing something
they should not have done, and arbitrarily inflates the tarball.
Per discussion with Soren, I have taken the 870-rc3 tarball directly
from open-iscsi's website, and
17 matches
Mail list logo
