Description of problem: kickstart iscsi root install does not use --target option even if specified. will use any target that may be available at --ipaddr. iscsi --ipaddr <ip> --target <iqn> also, when doing a manual install and selecting a specific target it will work but will not correctly report in /root/anaconda-ks.cfg. only reports: isci --ipaddr <ip> no --target, even though the manual installer works. Version-Release number of selected component (if applicable): Fedora 14 How reproducible: always Steps to Reproduce: 1. setup an iscsi target server with more than one target exported 2. use "iscsi --ipaddr <ip> --target <target>" in kickstart file 3. install will work but not use actual target specified (unless your lucky) 4. Actual results: specified target not used Expected results: specified target used Additional info: --target= shouldn't be ignored in ks.cfg and that writeKS should include it.
Proposing this as a blocker, user might end up installing on a different iscsi drive then intended.
Patch awaiting review: https://www.redhat.com/archives/anaconda-devel-list/2011-March/msg00143.html
Reporter, can you please test with updates=http://akozumpl.fedorapeople.org/bz676114.img and let me know if your issues are resolved? Thank you.
Discussed at 2011-03-11 blocker review meeting. Agreed that this is a final release blocker under criterion "The installer must be able to complete an installation using IDE, SATA, SCSI and iSCSI storage devices".
Fixed by 6733e0859e412a2693bddfc7dd718706a86474f0 f15, 43dbc98d1ad9d15e3f077bab34ff08039d2660db on master.
will test today/tomorrow and let you know - thanks.
sorry, i've added the update=http://<img> line to my kickstart for F14 and, despite the fact that it's documented as a valid option i get this back: The following error was found while parsing the kickstart configuration file: ... Unknown command: updates=http://akozumpl.fedorapeople.org/bz676114.img Can you help me, a gumby, with explicit instructions on how to integrate this to test (or a helpful URL that breaks this down). Thank you.
(In reply to comment #8) > sorry, i've added the update=http://<img> line to my kickstart for F14 and, > despite the fact that it's documented as a valid option i get this back: > > The following error was found while parsing the kickstart configuration file: > ... > Unknown command: updates=http://akozumpl.fedorapeople.org/bz676114.img Hi, yes, you need append the updates=... to the kernel boot command line, not to the kickstart. Sorry, I should have mentioned that. More documentation about the updates feature is here: http://fedoraproject.org/wiki/Anaconda/Updates
so included with the kernel args i see the update file get loaded but almost immediately following there is a python backtrace. Reproduced the backtrace with both fedora-14 and rhel-6.0 x86_64 typed the trace is something like: File "/tmp/updates/anaconda", line 480, in <module> (opts, args) = parseOptions() File "/tmp/updates/anaconda", line 169, in parseOptions from pyanaconda import _isys File "/tmp/updates/pyanaconda/__init__.py" in line 32, in <module> import iutil File "tmp/updates/pyanaconda/iutil.py" line 30, in <module> from flags import flags File "tmp/updates/pyanaconda/constants.py" line 59 in <module> import product File "/tmp/updates/pyanaconda/product.pm", line 35, in <module> config.read(["/tmp/product/.buildstamp", "/.buildstamp", os.environ.get("PRODBUILDPATH", "")]) File "/tmp/lib64/python2.6/ConfigParser.py", lne 286 in read self._read(fp, filename) File "/usr/lib64/python2.6/ConfigParser.py", line 486, in _read raise MissingSectionHeaderError(fpname, lineno, line) ConfigParser.MissingSectionHeaderError: File contains no section headers. file: /.buildstamp, line: 1 '201009221801.x86_64\n' install exited abnormally [1/1]
(In reply to comment #10) > so included with the kernel args i see the update file get loaded but almost > immediately following there is a python backtrace. Reproduced the backtrace > with both fedora-14 and rhel-6.0 x86_64 You need to test against a fedora 15. Also the recent F15 anaconda builds already have this patch applied so you shouldn't even need the updates image. Specifically you want a f15 image with at least anaconda-15.23-1.
ok - excellent Fedora-15-Alpha pulled today does not have the fix... but with the updates=http://<img> it installs to the specified --target and doesn't whack the other targets on the iscsi server when performing the "clearpart --all --initlabel" good fix. thank you for your help.
(In reply to comment #12) > ok - excellent Fedora-15-Alpha pulled today does not have the fix... but with > the updates=http://<img> it installs to the specified --target and doesn't > whack the other targets on the iscsi server when performing the "clearpart > --all --initlabel" > > good fix. thank you for your help. as_deniz, this should be fixed in Fedora 15 Beta, can you confirm whether the problem has been resolved? http://serverbeach1.fedoraproject.org/pub/alt/stage/15-Beta.RC2/
indeed it has been (checked with beta rc2 last week) - no longer requires the updates= with the kernel args - and completes iscsi --target install - tx for fix and the followup
thanks for testing.