Kernel dumps, provided by our customers, are uploaded by Customer Support to and shared via NFS to L3 servers at which they're analyzed. This procedure works, but likely has room for improvement.

The goal of the project is to understand the workflows and needs of Customer Support, L3 and engineering (Labs) and to implement a system to automate parts of the workflows.


  • Web interface to attach certain metadata to the coredump, e.g. bug number, timestamp, ...
  • Automatically add a comment to respective bugzilla entry (new dump available)
  • Set up the crash analysis environment (crash-setup)
  • Run a set of scripts to check for common issues

Looking for mad skills in:

crash bugzilla support l3

This project is part of:

Hack Week 16


Be the first to comment!

Similar Projects

QA Dashboard - provide a easy overview of the quality status of a product in development by xgonzo

QA uses a dashboard (SUSE internal: [http:/...

Bugzilla Sync for Taiga by suntorytimed

What is Taiga?

On the first view Taiga (...

bug screening helper by bmwiedemann

The Problem: many bugs filed for openSUSE go t...

crashsite by alnovak

Examining vmcore with crash (very) often means ...

Make sure bicho works with current bugzilla by dmacvicar

Bicho is a ruby gem to query bugzilla. I have r...