Jump to: navigation, search

Difference between revisions of "StarlingX/BugTemplate"

m
Line 7: Line 7:
 
  -----
 
  -----
 
  Appropriate title for the Issue should be given. Title should clearly state the defect.  
 
  Appropriate title for the Issue should be given. Title should clearly state the defect.  
  Example: [Bug] Controller swact fails after Backup & Restore
+
  Example: Controller swact fails after Backup & Restore
 
   
 
   
 
  Brief Description
 
  Brief Description

Revision as of 20:10, 27 August 2018

StarlingX bugs are reported/tracked in Launchpad: https://bugs.launchpad.net/starlingx

Please use the template below when opening StarlingX bugs.

Title
-----
Appropriate title for the Issue should be given. Title should clearly state the defect. 
Example: Controller swact fails after Backup & Restore

Brief Description
-----------------
Provide a brief description of the issue. Usually, it should not be more than 2 to 3 lines.
Example: After performing a restore of the system, user is unable to swact the controller. 

Severity
--------
Provide the severity of the defect.
<Critical: System/Feature is not usable after the defect>
<Major: System/Feature is usable but degraded>
<Minor: System/Feature is usable with minor issue>

Steps to Reproduce
------------------
Write down steps to reproduce the issue

Expected Behavior
------------------
Write down what was expected after taking the steps written above

Actual Behavior
----------------
State what is the actual behavior

Reproducibility
---------------
<Reproducible/Intermittent>
State if the issue is 100% reproducible or intermittent. If it is intermittent, state the frequency of occurrence

System Configuration
--------------------
<One node system, Two node system, Multi-node system, Dedicated storage, https, IPv4, IPv6 etc.>

Branch/Pull Time/Commit
-----------------------
Branch and the time when code was pulled or git commit

Timestamp/Logs
--------------
Provide a snippet of logs if available and the timestamp when issue was seen. 
Please indicate the unique identifier in the logs to highlight the problem
Provide a pointer to the logs for debugging (use attachments in Launchpad or paste.openstack.org)