WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.

Difference between revisions of "Reporting Bugs"

From Obsolete Lustre Wiki
Jump to navigationJump to search
Line 1: Line 1:
 
  
 
== Overview ==  
 
== Overview ==  
  
Despite the name, the Bugzilla for Lustre is really an issue tracker, not just a bug tracker. It's a one-stop repository for:
+
Despite the name, the [https://bugzilla.clusterfs.com Bugzilla for Lustre] is really an issue tracker, not just a bug tracker. It's a one-stop repository for:
 
+
** bugs
** bugs,
+
** enhancement requests
** enhancement requests,
 
 
** patch submission
 
** patch submission
** patch review, and dependency tracking.
+
** patch review, and dependency tracking
  
 
Email is a low-power and error-prone tool for these tasks, and a real bug tracking system is better in dozens of ways. For this reason we ask that all of the above issues be handled exclusively through Bugzilla.
 
Email is a low-power and error-prone tool for these tasks, and a real bug tracking system is better in dozens of ways. For this reason we ask that all of the above issues be handled exclusively through Bugzilla.

Revision as of 01:29, 25 June 2007

Overview

Despite the name, the Bugzilla for Lustre is really an issue tracker, not just a bug tracker. It's a one-stop repository for:

    • bugs
    • enhancement requests
    • patch submission
    • patch review, and dependency tracking

Email is a low-power and error-prone tool for these tasks, and a real bug tracking system is better in dozens of ways. For this reason we ask that all of the above issues be handled exclusively through Bugzilla.

All of the important links on this page are accessible from the front page or the toolbar at the bottom of each Bugzilla page, so you don't need to bookmark them. Searching for Bugs

There are two ways to search for bugs in Bugzilla: the quick way and the detailed way.

Use the quick way if you already know the bug number or just want to search for a keyword. Use the detailed way if you want to search on a specific field or with detailed or complex criteria.

If you want to use the detailed query, but don't really know what all of those things mean, you can read this longer guide.

Filing a Bug

Before visiting the bug reporting form, please take a moment to do a quick search to avoid filing duplicate bugs.

Please fill in as many fields as you can. If your version of Lustre isn't listed, please make a note of that in the bug summary so that we can correct that oversight. Please choose the correct component.

Most importantly, please write a good summary and comment. A descriptive summary will dramatically improve your chances of success, and a good comment will prevent it from being immediately closed as INVALID. At the minimum:

    • Describe the problem that you're solving, the feature that you're adding, or the enhancement that you're requesting.
    • If it's a bug, describe precisely the behaviour that you're seeing and the behaviour that you think is correct.
    • Provide as minimal a test case as possible. For example, if 'tar' is crashing, try to narrow it down to a specific syscall, and then do another test with just that one operation. If you tried to narrow it down without success, tell us what you tried.
    • If you have a patch, please read this page for information about how to create your patch, attach it to the bug, and have it reviewed. Please don't just paste it into a comment.

Priority Bugs

If you have a contract with Cluster File Systems for support of your Lustre project, you will see a group membership tick box. Use that to indicate that the bug is important for your project.

Developers

For bug management see the Lustre project Wiki