Description of problem:
Grubby is not able to find the kernel and react with a stacktrace: see screenshot
Version-Release number of selected component (if applicable):
Install fedora16 alpha 64 bit
Steps to Reproduce:
1.Install fedora16 alpha 64 bit
3.exeecute it and see
kdump and crash are also installed
Created attachment 520112 [details]
the stacktrace - python affected
That traceback is actually from kdump, do you have more details from grubby?
I mainly use openSUSE and be a bit without orientation on fedora.
So, you right. It´s a bug of kdump and not bug-buddy.
Please reassign it to one of yours which maintain on kdump.
This BZ should belong to system-config-kdump, not kexec-tools.
Thanks for the report.
Are you trying it on installed system or on live media? What is the architecture?
I´ve used KVM on fedora 15 to virtualise fedora16 alpha on x86_64 (CPU AMD T1100 when you want it exactly).
Can you please run as root in terminal `/usr/share/system-config-kdump/system-config-kdump-backend.py' and as a user in other terminal `system-config-kdump -d' and post here outputs?
The original vm is gone(see the date of the ticket!), so direct performing of your suggestion is not possible.
I´am low in time; do you think that getting the settings in a fedora16 final (fresh istall) would bring any benefit? -> Would take some time to do that, for me.
I've tried it now on fresh install of Fedora 16 and with all up2date I didn't hit this bug.
Now I hit the bug. Looks like it depends if you use grub or grub2.
I've hit this bug.
I'm using grubby --default-kernel as RPM %post section which return void.
As this case is not handled by my script, it fails. (xorg-x11-drv-nvidia FYI).
The installation was done with the update repository enabled from x86_64 DVD default installation (as of 20111230).
Sorry, I've miss-read the report, not my bug
(found it as #736188 sorry for the noise)
*** Bug 771819 has been marked as a duplicate of this bug. ***
There is new version available. Please test it and eventualy comment on bug #816230
*** This bug has been marked as a duplicate of bug 816230 ***