1REPORTER-BUGZILLA(1) LIBREPORT MANUAL REPORTER-BUGZILLA(1)
2
3
4
6 reporter-bugzilla - Reports problem to Bugzilla.
7
9 reporter-bugzilla [-vbf] [-g GROUP]... [-c CONFFILE]... [-F FMTFILE]
10 [-A FMTFILE2] -d DIR
11
12 Or:
13
14 reporter-bugzilla [-v] [-c CONFFILE]... [-d DIR] -t[ID] FILE...
15
16 Or:
17
18 reporter-bugzilla [-v] [-c CONFFILE]... [-d DIR] -t[ID] -w
19
20 Or:
21
22 reporter-bugzilla [-v] [-c CONFFILE]... -h DUPHASH [-p[PRODUCT]]
23
25 The tool reads problem directory DIR. Then it logs in to Bugzilla and
26 tries to find a bug with the same abrt_hash:HEXSTRING in Whiteboard.
27
28 If such bug is not found, then a new bug is created. Elements of DIR
29 are stored in the bug as part of bug description or as attachments,
30 depending on their type and size.
31
32 Otherwise, if such bug is found and it is marked as CLOSED DUPLICATE,
33 the tool follows the chain of duplicates until it finds a non-DUPLICATE
34 bug. The tool adds a new comment to found bug.
35
36 The URL to new or modified bug is printed to stdout and recorded in
37 reported_to element in DIR.
38
39 Option -t uploads FILEs to the already created bug on Bugzilla site.
40 The bug ID is retrieved from directory specified by -d DIR. If problem
41 data in DIR was never reported to Bugzilla, upload will fail.
42
43 Option -tID uploads FILEs to the bug with specified ID on Bugzilla
44 site. -d DIR is ignored.
45
46 Option -w adds bugzilla user to bug’s CC list.
47
48 Option -r sets the last url from reporter_to element which is prefixed
49 with TRACKER_NAME to URL field. This option is applied only when a new
50 bug is to be filed. The default value is ABRT Server"
51
52 Configuration file
53 If not specified, CONFFILE defaults to
54 /etc/libreport/plugins/bugzilla.conf and to user’s local
55 ~/.config/libreport/bugzilla.conf. Configuration file lines should have
56 PARAM = VALUE format. The parameters are: User’s local configuration
57 overrides the system wide configuration.
58
59 APIKey
60 API key for authentication to Bugzilla account.
61
62 BugzillaURL
63 Bugzilla HTTP(S) address. (default: https://bugzilla.redhat.com)
64
65 SSLVerify
66 Use yes/true/on/1 to verify server’s SSL certificate. (default:
67 yes)
68
69 Product
70 Product bug field value. Useful if you needed different product
71 than specified in /etc/os-release
72
73 ProductVersion
74 Version bug field value. Useful if you needed different product
75 version than specified in /etc/os-release
76
77 Parameters can be overridden via $Bugzilla_PARAM environment variables.
78
79 Formatting configuration files
80 Lines starting with # are ignored.
81
82 Lines can be continued on the next line using trailing backslash.
83
84 Format:
85
86 "%summary
87 summary format"
88
89 "section
90 element1[,element2]..." The literal text line to be added to
91 Bugzilla comment. Can be empty. (Empty lines are NOT ignored!)
92
93 Summary format is a line of text, where %element% is replaced by
94 text element's content, and [[...%element%...]] block is used only if
95 %element% exists. [[...]] blocks can nest.
96
97 Sections can be:
98 - %summary: bug summary format string.
99 - %attach: a list of elements to attach.
100 - text, double colon (::) and the list of comma-separated elements.
101
102 Elements can be:
103 - problem directory element names, which get formatted as
104 <element_name>: <contents>
105 or
106 <element_name>:
107 :<contents>
108 :<contents>
109 :<contents>
110 - problem directory element names prefixed by "%bare_",
111 which is formatted as-is, without "<element_name>:" and colons
112 - %oneline, %multiline, %text wildcards, which select all corresponding
113 elements for output or attachment
114 - %binary wildcard, valid only for %attach section, instructs to attach
115 binary elements
116 - problem directory element names prefixed by "-",
117 which excludes given element from all wildcards
118
119 Nonexistent elements are silently ignored.
120 If none of elements exists, the section will not be created.
121
122 Integration with ABRT events
123 reporter-bugzilla can be used as an ABRT reporter. Example fragment for
124 /etc/libreport/report_event.conf:
125
126 # Report Python crashes
127 EVENT=report_Bugzilla analyzer=Python
128 reporter-bugzilla -d . -c /etc/libreport/plugins/bugzilla.conf
129
131 -d DIR
132 Path to problem directory.
133
134 -c CONFFILE
135 Path to configuration file.
136
137 -b
138 When creating bug, attach binary files too.
139
140 -f
141 Force reporting even if this problem is already reported.
142
143 -F CONF_FORMAT_FILE
144 Formatting file for initial comment. Default:
145 /etc/libreport/plugins/bugzilla_format.conf
146
147 -A CONF_FORMAT_FILE
148 Formatting file for duplicates. Default:
149 /etc/libreport/plugins/bugzilla_format.conf
150
151 -t[ID]
152 Upload FILEs to the already created bug on Bugzilla site.
153
154 -w
155 Add bugzilla user to CC list [of bug with this ID]. Applicable only
156 with -t.
157
158 -h, --duphash DUPHASH
159 Search in Bugzilla by abrt’s DUPHASH and print BUG_ID.
160
161 -p[PRODUCT], --product[PRODUCT]
162 Specify a Bugzilla’s product (ignored without -h). Default:
163 "Fedora". If only -p or --product without PRODUCT is presented
164 either value from environment variable Bugzilla_Product in the
165 first place or REDHAT_BUGZILLA_PRODUCT value from /etc/os-release
166 is used.
167
168 -g, --group GROUP
169 When creating a new ticket restrict access to this group only.
170
172 Environment variables take precedence over values provided in the
173 configuration file.
174
175 Bugzilla_APIKey
176 API key for authentication to Bugzilla account.
177
178 Bugzilla_BugzillaURL
179 Bugzilla HTTP(S) address. (default: https://bugzilla.redhat.com)
180
181 Bugzilla_SSLVerify
182 Use yes/true/on/1 to verify server’s SSL certificate. (default:
183 yes)
184
185 Bugzilla_Product
186 Product bug field value. Useful if you needed different product
187 than specified in /etc/os-release
188
189 Bugzilla_ProductVersion
190 Version bug field value. Useful if you needed different product
191 version than specified in /etc/os-release
192
193 Bugzilla_PrivateGroups
194 List of Bugzilla group names that will be set to the new bug if
195 Bugzilla_CreatePrivate equals yes
196
197 Bugzilla_CreatePrivate
198 Use yes/no to control whether the new bug should have set groups
199 listed in Bugzilla_PrivateGroups
200
201 Bugzilla_DontMatchComponents
202 Comma-separated list of package components (e.g. selinux-policy,
203 anaconda) for which reporter-bugzilla should not use Bugzilla
204 component match when searching for duplicate bug reports.
205
206 http_proxy
207 the proxy server to use for HTTP
208
209 HTTPS_PROXY
210 the proxy server to use for HTTPS
211
213 /usr/share/libreport/conf.d/plugins/bugzilla.conf
214 Readonly default configuration files.
215
216 /etc/libreport/plugins/bugzilla.conf
217 Configuration file.
218
219 ~/.config/libreport/bugzilla.conf
220 User’s local configuration file.
221
222 /etc/libreport/plugins/bugzilla_format.conf
223 Configure formating for reporting.
224
226 report_event.conf(5), bugzilla_format.conf(5)
227
229 • ABRT team
230
231
232
233LIBREPORT 2.17.11 07/20/2023 REPORTER-BUGZILLA(1)