blob: b56ecb7101a21f35e2bc99bf8b75ccd94ec63198 [file] [log] [blame]
Tim Düsterhusbbab3bf2021-06-23 21:38:13 +02001name: Bug Report
2description: Report a problem with HAProxy to help us resolve it.
3labels:
4- 'type: bug'
5- 'status: needs-triage'
6body:
7- type: markdown
8 attributes:
9 value: |
10 ## Welcome!
11
12 You are about to *report a bug* you encountered in HAProxy. Please use the 'Feature Request' template if you want to propose a new feature instead.
13
14 This issue tracker is used to track actual bugs. Please use [the forum](https://discourse.haproxy.org/) or mailing list if you have a question, e.g. to get help with building a configuration to achieve your desired behavior.
15
16 The forum is at: https://discourse.haproxy.org/
17
18 The mailing list (no need to subscribe) is: haproxy@formilux.org
19 Subscribe to the list: haproxy+subscribe@formilux.org
20 Unsubscribe from the list: haproxy+unsubscribe@formilux.org
21
22 Forum and mailing list are correct places for questions about HAProxy or general suggestions and topics, e.g. usage or documentation questions! This issue tracker is for tracking bugs and feature requests directly relating to the development of the software itself.
23
24 Thanks for understanding, and for contributing to the project!
25- type: textarea
26 id: description
27 attributes:
28 label: Detailed Description of the Problem
29 description: |
30 In this section, please try to concentrate on observations. Only describe what you observed directly.
31 validations:
32 required: true
33- type: textarea
34 id: expected-behavior
35 attributes:
36 label: Expected Behavior
37 description: |
38 Explain why you consider the described behavior (above) to be wrong. What did you expect instead?
39
40 Most likely this is a mismatch between HAProxy's documentation and HAProxy's behavior.
41 validations:
42 required: true
43- type: textarea
44 id: steps
45 attributes:
46 label: Steps to Reproduce the Behavior
47 description: |
48 The more time you spend describing an easy way to reproduce the behavior (if this is possible), the easier it is for the project developers to fix it!
49 placeholder: |
50 1.
51 2.
52 3.
53 validations:
54 required: true
55- type: textarea
56 id: possible-cause
57 attributes:
58 label: Do you have any idea what may have caused this?
59 description: |
60 Simply leave this empty if you do not.
61- type: textarea
62 id: possible-solution
63 attributes:
64 label: Do you have an idea how to solve the issue?
65 description: |
66 Simply leave this empty if you do not.
67- type: textarea
68 id: configuration
69 attributes:
70 label: What is your configuration?
71 description: |
72 - Include as much configuration as possible, including global and default sections.
73 - Replace confidential data like domain names and IP addresses.
74 render: haproxy
75 validations:
76 required: true
77- type: textarea
78 id: haproxy-vv
79 attributes:
80 label: 'Output of `haproxy -vv`'
81 description: |
82 Please run `haproxy -vv` (with two `v`) and paste the output into this field.
83
84 Please also include the output of `uname -a` if you use HAProxy 2.1 or older.
85 render: plain
86 validations:
87 required: true
88- type: textarea
89 id: last-output
90 attributes:
91 label: Last Outputs and Backtraces
92 description: |
93 If HAProxy crashed then please provide:
94
95 1. The last output from your HAProxy logs (e.g. from journalctl or syslog).
96 2. A backtrace from a coredump (`t a a bt full`).
97 render: plain
98- type: textarea
99 id: additional
100 attributes:
101 label: Additional Information
102 description: |
103 Any additional information about your environment that may be useful to know about. For example:
104
105 - Any local patches applied
106 - Environment specificities
107 - Unusual workload
108 - Interesting observations or coincidences with events on other components