Created attachment 742787 [details]
Description of problem:
After installing F19-Alpha (and some previous versions) I no longer have an /etc/sysconfig/kernel file. kickstart install.
Version-Release number of selected component (if applicable):
Couple different systems.
Still the case with 19.28-1. This prevents future kernel installs from becoming the default kernel.
Please attach logfiles as individual text/plain files.
Created attachment 751774 [details]
Created attachment 751780 [details]
This seems to be the relevant bit:
21:29:13,163 INFO anaconda: Installing bootloader
21:29:13,163 INFO anaconda: bootloader stage1 target device is vda
21:29:13,164 INFO anaconda: bootloader stage2 target device is vda3
21:29:13,166 DEBUG anaconda: new default image: <pyanaconda.bootloader.LinuxBootLoaderImage objec
t at 0x7feec03cd590>
21:29:13,188 ERR anaconda: failed to get package name for default kernel
Please try with a newer version, and include all the logs if it is still happening. Also, does the installed system boot?
Created attachment 751876 [details]
Same issue with 19.29-1 from F19 Beta RC3. I don't know how to get any newer than that.
System boots fine, but new kernels are not installed as the default, so system continues to boot the original kernel unless /etc/grub2.cfg is edited by hand.
Created attachment 751877 [details]
Created attachment 751888 [details]
Created attachment 751889 [details]
Created attachment 751890 [details]
Created attachment 751891 [details]
Orion: I suspect the lack of /etc/sysconfig/kernel was not actually the cause of the problem you were seeing. I suspect you tried to install a Rawhide kernel and hit https://bugzilla.redhat.com/show_bug.cgi?id=965897 . Yes? I just tried doing a 'yum update kernel' with no /etc/sysconfig/kernel , and the updated fc19 kernel was added to grub2 as the default kernel.
Discussed at 2013-05-29 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-29/f19final-blocker-review-1.2013-05-29-16.02.log.txt . Rejected as a blocker as it doesn't seem to be causing the symptom claimed according to my testing, but accepted as a freeze exception issue since there's no good reason not to ship the file, so we might as well fix this, and the fix seems safe.
Also fixed in 19.30.1-1, which is now in updates-testing.
verified fixed in 19.31.1.
We're well past 19.30.1 now, so closing.