Bug 208671 - Crash following attempt to add iSCSI drive
Crash following attempt to add iSCSI drive
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
Blocks: FC6Blocker
  Show dependency treegraph
Reported: 2006-09-29 19:51 EDT by ray hammond
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-10-02 18:04:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Exception dump (80.96 KB, text/plain)
2006-09-29 19:54 EDT, ray hammond
no flags Details

  None (edit)
Description ray hammond 2006-09-29 19:51:58 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)

Description of problem:
On attempting to add a new iSCSI drive an exception is raised.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Opt to start the GUI version of the installer.
2. Press next on the welcome screen, select Install anyway on the pop-up.
3. Select English (English) as your language and press Next.
4. Select United kingdom for keyboard and press Next.
5. Select install fedora core and press next.
6. Click the button labelled "Advanced storage configuration".
7. Ensure add iSCSI radio button is selected and press Add.
8. Enter an IP address of and enter a name of test1.
9. Press Add target.

Actual Results:
An exception occured.

Expected Results:
The iSCSI device should be detected.

Additional info:
Comment 1 ray hammond 2006-09-29 19:54:29 EDT
Created attachment 137455 [details]
Exception dump

Exception dumped by anaconda
Comment 2 ray hammond 2006-09-29 20:01:28 EDT
I later noticed that I typed the wrong IP address '', I guessed that 
this was what caused the exception.  However; I tried again with the correct IP 
and got the same error.
Comment 3 Jeremy Katz 2006-10-02 18:04:57 EDT
Should be fixed

Note You need to log in before you can comment on or make changes to this bug.