Red Hat Bugzilla – Bug 405911
Anaconda fails to configure iSCSI initiator
Last modified: 2008-01-16 15:24:57 EST
Description of problem:
Anaconda fails to configure iSCSI initiator to connect to my iSCSI target. I
Version-Release number of selected component (if applicable):
anaconda-220.127.116.11-1 with with partedUtils.py fix.
Steps to Reproduce:
1. Advanced storage configuration
2. add iSCSI target
"InitiatorAlias= is required"
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?
Created attachment 273841 [details]
(accidentelly attached, ignore)
Created attachment 273861 [details]
Created attachment 273891 [details]
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)
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
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.
Ping on this. Anything I can do to help resolve the issue?
We weren't even including the module in the images to begin with. This should
be fixed in the next build of anaconda.