Description of problem:
I did not check the 'enable kdump' checkbox in firstboot. However, the kdump server is still set up to start.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 415745 [details]
patch to have kdumpEnabled shadow checkbox status
Bill, do me a favor and confirm that this fixes the issue for you. Thanks!
This did not fix it for me.
*** Bug 596337 has been marked as a duplicate of this bug. ***
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
*** Bug 601054 has been marked as a duplicate of this bug. ***
It is pretty awful to have a big warning icon appear in GDM for many users because of this.
It makes a really bad impression if on boot after a fresh install you get a service failing and a alert icon shows up on the GDM screen. We definitely need to fix this one.
Created attachment 430704 [details]
sorry I missed an early exit case. This patch should ensure that we chkconfig kdump off as soon as we apply changes in firstboot. I also fixed a few nagging warnings in the module at the same time. This is working in my testing here. Please confirm, and I'll get this comitted.
- upgrade box to latest tree
- remove firstboot, kexec-tools, system-config-kdump
- reinstall those packages
- patch with the included patch
I get 'insufficient memory to configure kdump', and have to continue. (This is new, the last time I suspect these memory limits weren't there.)
In that session's GDM, I have a warning that says kdump startup failed.
On subsequent reboots, there are no errors.
So, the question is - is the error on the first boot enough to worry about?
yeah, that error is ok, thats a fix for a different bug. You'll get the kdump start failed error on the firstboot boot if you don't have memory reserved, since you'll always start kdump then, and since you didn't get subsequent errors, it sounds like firstboot correctly turned of the kdump service for you. I'll commit this. Thanks!
*** Bug 620514 has been marked as a duplicate of this bug. ***
Verified with -139.el6:
[root@ibm-x3655-05 ~]# yum list kernel kexec-tools firstboot system-config-kdump
Loaded plugins: rhnplugin
This system is not registered with RHN.
RHN support will be disabled.
firstboot.x86_64 1.110.8-1.el6 @beaker-os
kernel.x86_64 2.6.32-64.el6 installed
kexec-tools.x86_64 2.0.0-139.el6 installed
system-config-kdump.noarch 188.8.131.52-2.el6 @beaker-os
Change status to VERIFIED.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.