During firstboot the firstboot kdump module tells me that kdump cannot be configured due to low memory. This is fine, but it leaves the kdump init script enabled. Resulting in a FAILED message during startup every boot, and showing the there are boot errors icon in gdm every boot.
I think that the kdump firstboot module should disable the kdump initscript
when there is not enough memory to configure kdump.
This feature request has been proposed after Feature Freeze and we
are unable to resolve it in time for the current Red Hat Enterprise
Linux release. It has been denied for the current release and
proposed for the next Red Hat Enterprise Linux release.
I believe this a dup of bug 594830?
(In reply to comment #3)
> I believe this a dup of bug 594830?
Ah yes, you're right, marking as dup.
*** This bug has been marked as a duplicate of bug 594830 ***