Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 982642

Summary:	spacewalk-abrt doesn't report kernel crash via abrt-addon-vmcore
Product:	Red Hat Satellite 5	Reporter:	Rich Jerrido <rjerrido>
Component:	Client	Assignee:	Milan Zázrivec <mzazrivec>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Matej Kollar <mkollar>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	560	CC:	cperry, jhutar, mkollar
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	spacewalk-abrt-2.0.1-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-01 20:10:53 UTC	Type:	Bug
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:	1002041
Bug Blocks:	924199

Description Rich Jerrido 2013-07-09 13:22:04 UTC

Description of problem:

spacewalk-abrt does not report kernel crashes reported via the abrt-addon-vmcore plugin. 

Version-Release number of selected component (if applicable):
spacewalk-abrt-1.9.6-2.el6sat.noarch
abrt-2.0.8-15.el6.x86_64
abrt-addon-vmcore-2.0.8-15.el6.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Install the above packages on the client
2. Configure client system to use kdump. Ensure kdump is operational (service kdump status) 
3. Crash the system (echo c > /proc/sysrq-trigger)

Actual results:
On the system's Software crash page (https://fqdn/rhn/systems/details/SoftwareCrashes.do?sid=<systemid>), the crash is not reported. 


Expected results:
The kernel crash should be reported, similar to other crashes captures by abrt (such as kernel oops, python tracebacks, etc). 


Additional info:


[*] Running 'abrt-cli list' does show the kernel crash being reported to abrt. 
[*] Running 'spacewalk-abrt -v --sync' to see if the crash could be manually uploaded does not work either.

Comment 2 Milan Zázrivec 2013-07-10 09:15:15 UTC

Not a limitation -- the vmcore crash dir just looks different from
what our tools expected.

Fixed in spacewalk.git master: 2979bdf31c4000f0be509daa6bacccf7fc6feacf

Comment 5 Clifford Perry 2013-10-01 20:10:53 UTC

This bug was fixed with updated packages being released within the RHN Tools
channels. 


RHN Tools (for Sat 5.6 GA) Errata text:

https://rhn.redhat.com/errata/RHEA-2013-1391.html