Created attachment 604054 [details] Screen shot of vm failed boot Description of problem: Using koan to try to install F18-Alpha-TC1 vm fails. See attached screen shot. Some perhaps relevant error messages: dracut-pre-udev[214]: //lib/dracut/hooks/pre-udev/40-kickstart-gengrules.sh: line 7: wait_for_kickstart: command not found dracut-initqueue[290]: Warning: Could not boot. dracut-cmdline[57]: //lib/dracut/hooks/cmdline/24-anaconda-modprobe.sh: line 20: basename: command not found dracut-cmdline[57]: FATAL: Module iscsi_tcp not found. dracut-cmdline[57]: FATAL: Module iscsi_ibft not found. dracut-cmdline[57]: FATAL: Module sha256 not found.
Probably the same as 847644, right?
Quite possibly has the same solution, but they are different boot paths. I'll let the anaconda folks decide. Otherwise let's wait until the next compose.
Created attachment 604782 [details] Screenshot of failed boot Different, but still no go with Alpha TC2. Sorry, but just too hard to transcribe on my netbook. Will try do so in the morning.
dracut-pre-udev[206]: //lib/dracut/hooks/pre-udev/40-kickstart-gengrules.sh: line 7: wait_for_kickstart: command not found dracut-initqueue[286]: /lib/dracut/hooks/initqueue/settled/00-anaconda-ks-sendheaders.sh: line 16: set_http_header: command not found
That now seems to be specific to kickstart installs, so let's keep the bug open.
This looks like another case of a missing sourceing of necessary library. Dracut changed recently and now imports are carrying over from one phase to the next. Should be a simple fix, I'll work up a patch soon, if wwoods doesn't beat me to it.
Proposing as a Beta blocker; kickstart is in the Beta criteria.
Patch posted.
anaconda-18.6-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.6-1.fc18
Package anaconda-18.6-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.6-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-12095/anaconda-18.6-1.fc18 then log in and leave karma (feedback).
Created attachment 605206 [details] anaconda screenshot WIth TC3, the set_http_header message is gone, but the wait_for_kickstart line is still there and it still fails to boot.
New patch posted.
anaconda-18.6-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Reopening. Not yet fixed.
(In reply to comment #14) > Reopening. Not yet fixed. That doesn't help without more details/logs.
See attachment and comment 11 for TC3 failures. When TC4 arrives (hopefully with patch from comment 12) I'll update.
Created attachment 610091 [details] anaconda screenshot Okay, with TC5 now it's choking on the cobbler use of: %include /tmp/pre_install_network_config in the main kickstart section. I believe we ran into similar before. Open a new bug, or keep on this one?
orion: what's the status with Alpha final?
Exactly the same as TC5. So I imagine it may work for many kickstarts, just not the one I use (from cobbler) that uses an include file in the main section that is generated in %pre. Happy to file a new bug, or perhaps just change the title of this one? We ran into this a well in an earlier release. I could probably dig up the bug if it would be helpful.
Discussed at 2012-09-26 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-09-26/f18-beta-blocker-review-1.2012-09-26-16.03.log.txt . The relevant criterion here is "The installer must be able to successfully complete a scripted installation, using the installer's preferred scripting system, which duplicates the default interactive installation as closely as possible". The criterion about 'kickstart delivery methods' does not apply here, as *delivering* the kickstart certainly worked. The relevant criterion is intentionally minimalistic: what it really means (per https://lists.fedoraproject.org/pipermail/test/2011-August/102368.html ) is 'if you do an all-defaults click-through interactive install of the Beta, then take the generated /root/anaconda-ks.cfg kickstart and feed it back into the installer, it should work'. That's the _only_ 'supported configuration', it's a strictly interpreted criterion, not an open one. This issue does not violate that criterion, on the information provided so far. However, we don't reject this bug, as the idea with regard to kickstart criteria was that we'd have that criterion as a baseline and we could then look at individual cases to decide what more we wanted to support in terms of kickstart functionality. This is obviously an individual case we could evaluate and decide if we think whatever is broken is important enough to add it to the criteria, but first we need to know precisely what's broken, which at present we don't. Therefore, we decided to delay the decision on this bug until we have a clearer understanding of what is broken.
Discussed at 2012-10-03 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-03/f18-beta-blocker-review-2.2012-10-03-16.00.log.txt . The above note still stands, we did not yet get information on what's broken here. Tim Flink will try and reproduce the bug and poke anaconda team to look into it.
Bug 805316 was the one I was thinking of, but apparently that is somewhat different. In any case this is still present in F18 Beta TC2. I really hope this is fixed soon as I believe it's going to break a lot of cobbler driven installs. My whole infrastructure is driven by cobbler, so I'm really not going to be able to do any real testing of F18 until this is fixed.
that's certainly the kind of factor we can take into account in building out the requirements for kickstart functionality.
Discussed at 2012-10-10 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-10/f18beta-blocker-review-3.2012-10-10-16.05.log.txt . Agreed we still are waiting for clear data on exactly what's broken here (though the info that it affects cobbler deployments helps). Tim didn't get around to looking into it last week, he will do so this week.
Created attachment 627506 [details] working kickstart with %include url I tried to reproduce with the attached kickstart using F18 Beta TC4. The kickstart contains: > %include http://kparal.fedorapeople.org/tmp/incl.ks and the included file contained just: > selinux --disabled Everything worked. That means "%include <url>" is OK. That means either "%include <file>" is broken, or you need even more magic to break it.
Orion, please include the kickstart file that breaks your installs, thank you.
Created attachment 627555 [details] kickstart with %Include generated by %pre Here's a simple example. The file to be %included is generated by the %pre section. This is a pretty standard cobbler generated kickstart file. Ah, but I've found the problem now! No more ifconfig! So this is really a cobber issue. if ifconfig -a | grep -i 00:16:3e:55:a7:2d then IFNAME=$(ifconfig -a | grep -i '00:16:3e:55:a7:2d' | cut -d " " -f 1) if [ -z $IFNAME ]; then IFNAME=$(ifconfig -a | grep -i -B 2 '00:16:3e:55:a7:2d' | sed -n '/flags/s/:.*$//p') fi echo "network --device=$IFNAME --bootproto=dhcp" >> /tmp/pre_install_network_config fi + grep -i 00:16:3e:55:a7:2d + ifconfig -a /tmp/ks-script-bXE6OO: line 8: ifconfig: command not found
CURRENTRELEASE isn't an appropriate resolution, changing to NOTABUG, as it really wasn't. Also dropping blocker status so we don't count this as some sort of fixed blocker in any kind of statistical analysis we do.
Well, the original problem was a bug :), but yes the second issue and current title of the bug was not. Thanks.