Bug 1318367

Summary: vmcore failing in retrace_log with 'prepare_debuginfo failed: Unable to determine kernel version' generates RetraceWorker backtrace in /var/log/httpd/error_log
Product: [Fedora] Fedora EPEL Reporter: Dave Wysochanski <dwysocha>
Component: retrace-serverAssignee: Michal Toman <michal.toman>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: el6CC: jberan, michal.toman, phelia
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: 2017-04-28 21:46:06 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:

Description Dave Wysochanski 2016-03-16 16:34:54 UTC
Description of problem:
As of the latest upstream retrace-server, if we fail to detect the kernel version we now see the following message in /var/log/httpd/error_log:
Traceback (most recent call last):
  File "/usr/bin/retrace-server-worker", line 64, in <module>
    worker.start(kernelver=kernelver, arch=cmdline.arch)
  File "/usr/lib/python2.6/site-packages/retrace/retrace_worker.py", line 910, in start
    self._fail()
  File "/usr/lib/python2.6/site-packages/retrace/retrace_worker.py", line 148, in _fail
    raise RetraceWorkerError(errorcode=errorcode)
retrace.retrace.RetraceWorkerError: None


Version-Release number of selected component (if applicable):
retrace-server-1.14-2.el6

How reproducible:
Every time

Steps to Reproduce:
1. submit a vmcore which will fail due to kernel detection (either a custom kernel, or one such as in https://bugzilla.redhat.com/show_bug.cgi?id=1149356

Actual results:
Backtrace in /var/log/httpd/error_log if we can't detect the kernel version on a vmcore


Expected results:
No backtrace but some error message indicating the kernel version detection failed (we already have this in retrace_log - maybe point there for the task?)

Additional info:
Low impact / priority.  I filed this bug as I don't think this is the intent of the error handling and it may be a good cleanup at some point.

Comment 1 Dave Wysochanski 2017-04-28 21:46:06 UTC
I'm pretty sure this has been fixed with all the refactoring that was done.  I've not seen this problem in a long time so closing CURRENTRELEASE.