Red Hat Bugzilla – Bug 976446
kdump fails to start on initial installation
Last modified: 2014-02-21 00:51:16 EST
Description of problem:
When booting the iso the kdump services fails to start and this may confuse the user.
Steps to Reproduce:
1. Boot ISO
Boot log or console shows [FAILED] on kdump start
kdump should not start or should not fail.
adds a wrapper script and only starts if a kdump configuration is persisted
Created attachment 763654 [details]
attached the boot console screen
Can reproduce this bug on build rhev-hypervisor6-6.4-20130528.0.el6_4
Please see the attached screenshot for boot console to check this issue.
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Still could see kdump start issue on boot console screen, so this bug wasn't fix in ovirt-node-3.0.1-7.el6. need to re-assigned it.
(In reply to haiyang,dong from comment #7)
> Test version:
I could also reproduce it with
Now see ovirt-kdump start success on boot console screen, so this bug has been fixed, change the status into "verified"
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.