Bug 242379

Summary: anaconda crashes when configuring iSCSI (DHCP address!)
Product: [Fedora] Fedora Reporter: Michael Rommel <rommel>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 7   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-06-04 10:10:49 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
anaconda crash log none

Description Michael Rommel 2007-06-03 16:42:43 EDT
Description of problem:

While configuring iSCSI, anaconda crashes. This is while using 
a DHCP address, I didn't try a static address (reported in other
bug reports).

anaconda complains in the exception details, after attempting
iscsiadm: "no record found", see attached message.

Using a shell on the system and running exactly the same command,
it prints:,1 iqn.2007-03.net-layer-7.blackbird:storage.seagull

which is the iSCSI target that has been set up.

Affected version: standard Fedora 7 anaconda installer

How reproducible:

Steps to Reproduce:
1. Click on "Advanced storage configuration"
2. Add iSCSI target
3. Enter as IP Address and
iqn.2007-03.net-layer-7.blackbird:storage.seagull as target
Actual results:

Exception occurred

Expected results:

Mount of the iSCSI target as disk

Additional info:
Comment 1 Michael Rommel 2007-06-03 16:42:43 EDT
Created attachment 156036 [details]
anaconda crash log
Comment 2 Chris Lumens 2007-06-04 10:10:49 EDT
This will be fixed in the next build of anaconda.  The fix may also be included
in an updates.img which would allow you to use the released version of anaconda
for working around this bug.  If that happens, I will update this bug report to
explain it.
Comment 3 Chris Lumens 2007-06-06 13:47:43 EDT
This bug is now addressed by an updates image.  It is available for download at:


Instructions for using updates disks are located at:


If possible, please test this image out and report if it fixes your issue or
not.  Once we are confident that your issue is solved by this image, we are
going to announce it more publicly.  This fix may also be included in an updated
anaconda package later for people who are making custom Fedora distributions. 
Thanks for your time.