Bug 805778

Summary: port and sync with latest rhel6 kdump.init
Product: [Fedora] Fedora Reporter: Dave Young <ruyang>
Component: kexec-toolsAssignee: Dave Young <ruyang>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: nhorman, ruyang, xiyou.wangcong
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-31 03:26:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 799340    

Description Dave Young 2012-03-22 05:58:48 UTC
Description of problem:

* Review and port latest kdump.init logic into fedora kdumpctl

related rhel6 bzs need review after the porting:
bz592312,"kdump's dumprd not rebuilding when appropriate."
bz544161,"Kdump initscript doesn't return the correct code"
bz611693,"kdump doesn't use init.d script to save vmcore any longer"
bz731394,"[kexec-tools] Remove warning when kdump service starts"
bz598067,"[FEAT RHEL6.2]  Provide verification tool to check config files"
bz600595,"kdump service script needs a condrestart"
bz748748,"improve mount -t debugfs logic in kdump service scrip

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Fedora Admin XMLRPC Client 2012-04-16 06:11:55 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Dave Young 2012-08-31 03:26:04 UTC
All bugs are addressed or not valid for latest fedora.

One thing is 748748 fixed the debugfs mounting logic. In fedora kexec-tools kdumpctl we do not try to mount debugfs without seeing any problem. Will address this issue if we encounter such issue in the futuer.