Red Hat Bugzilla – Full Text Bug Listing
|Summary:||Anaconda fails to configure iSCSI initiator|
|Product:||[Fedora] Fedora||Reporter:||Lubomir Kundrak <lkundrak>|
|Component:||anaconda||Assignee:||Anaconda Maintenance Team <anaconda-maint-list>|
|Status:||CLOSED RAWHIDE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2008-01-16 15:24:57 EST||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Lubomir Kundrak 2007-11-30 09:44:19 EST
Description of problem: Anaconda fails to configure iSCSI initiator to connect to my iSCSI target. I attach screenshots. Version-Release number of selected component (if applicable): anaconda-22.214.171.124-1 with with partedUtils.py fix. Steps to Reproduce: 1. Advanced storage configuration 2. add iSCSI target Actual results: "InitiatorAlias= is required" Additional info: It would be very nice, if the iSCSI target address could be entered as DNS name, not only IP address. I this is just too small change to have a feature report on its own, or isn't it?
Comment 1 Lubomir Kundrak 2007-11-30 09:44:19 EST
Created attachment 273841 [details] (accidentelly attached, ignore)
Comment 5 Lubomir Kundrak 2007-11-30 10:00:30 EST
Created attachment 273911 [details] The anaconda exception log I attach it just now, I had some trouble getting it off the machine (bug #405951, bug #405921)
Comment 6 Lubomir Kundrak 2007-11-30 11:35:46 EST
While the exception in the log above has been fixed, iSCSI still can not be configured. InitiatorAlias is apparently not needed, iscsiadm [*] complains about configuration error. If I copy the iscsid.conf I use from my workstation (about the same one that came with the package), iscsiadm no longer complains, but still it doesn't list the targets. iscsid keeps complaining about not knowing anything about UID 0, which resembles bug #405921. [*] iscsiadm --mode discovery --type sendtargets --portal 172.31.2.246
Comment 7 Lubomir Kundrak 2007-12-10 15:05:58 EST
After bug #405921 was resolved, symptoms changed, but iSCSI is still unusable. Now the initiator can not be configured due to another reason -- lack of crc32c kernel module. Anaconda should insmod crc32c before attempting to configure the initiator. See #208607 for more details.
Comment 8 Lubomir Kundrak 2008-01-14 03:41:48 EST
Ping on this. Anything I can do to help resolve the issue?
Comment 9 Chris Lumens 2008-01-16 15:24:57 EST
We weren't even including the module in the images to begin with. This should be fixed in the next build of anaconda.