Bug 198577 - Starting with 2.6.17-1_FC5 kernel, iscsi initiator gives error 22
Summary: Starting with 2.6.17-1_FC5 kernel, iscsi initiator gives error 22
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: iscsi-initiator-utils
Version: 5
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Mike Christie
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-12 01:09 UTC by Mark C. Davis
Modified: 2012-06-26 16:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-06-20 17:46:41 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Mark C. Davis 2006-07-12 01:09:13 UTC 
Description of problem:
On systems configured correctly with iscsi initiators, upgrading to 2.6.17-1
kernel causes node login to fail with error 22.

Version-Release number of selected component (if applicable):
FC5, 2.6.17-1_FC kernel
iscsi-initiator-utils 5.0.5.476-0.1

How reproducible:
do iscsi node login

Steps to Reproduce:
1. boot FC 5 2.6.17-1,
2. service iscsi start
3. iscsiadm -m node -r xxxxx -l
  
Actual results:
service hangs, error 9 is displayed on console, error 22 is logged in messages

Expected results:
no output (successful login)

Additional info:
works properly in FC6 2.6.17
Comment 1 Mike Christie 2006-07-13 16:14:48 UTC 
Sorry about this. The FC5 kernel and the rpm got out of sync. I did not know the
FC5 kernel was going to contain the FC6 kernels drivers so the FC6 iscsi rpm got
update but the FC5 one did not.

I am in the process of adding some bugfixes to both kernels and updating both
FC5 and FC6's rpm.
Comment 2 Chris Tatman 2006-08-04 20:35:01 UTC 
Yep.  I just got bit by this one today too.  Please let me know if you need any
testers for the fix!
Comment 3 Mike Christie 2006-08-10 07:47:11 UTC 
This should be fixed on the next FC kernel update.
Comment 4 Mark C Davis 2006-11-02 17:55:51 UTC 
This fix works for me.
Comment 5 Mike Christie 2007-06-20 17:46:41 UTC 
Closing bug since it was fixed upstream and that works for reporter.
Note You need to log in before you can comment on or make changes to this bug.