Bugzilla - Triage Connector Issues

Document created by JohnStreeter Employee on Oct 18, 2016Last modified by SamCreek on Apr 19, 2017
Version 4Show Document
  • View in full screen mode
Here are some ideas for triaging Bugzilla connector issues: 

 

NOTE: Throughout these steps below, please replace "localhost:3000" with the actual URL for 
your BUGZILLA server. This would be the URL used in the <Url>....</Url> tag within the 
<BugzillaConnection> section of the XML file. 

 


1) Remember that the script "script/bugzilla_api_server.pl" must be invoked before starting the connector.  Starting the connector without running this script will generate an error (like "can not connect to server"). 

 

To run the script, issue two commands, something like:

cd /var/www/0.9 
script/bugzilla_api_server.pl 

 

2) Navigate to this URL in your browser: http://localhost:3000/ .  Does the "Welcome to the world of Catalyst." display? 

 

The banner should look something like



Bugzilla::API on Catalyst 5.80030 

 

3) Navigate to this URL in your browser: http://localhost/bugzilla/ . 

 

The "Welcome to Bugzilla" page should display:

 

 

4) Navigate to this URL in your browser: http://localhost:3000/bug/37000/ (again, please use your value for localhost:port).

 

You should see the details page for bug id "37000", which looks similar to:

 
--- 
assigned_to: 
name: integrations 
real_name: Integrations 
cf_copy_to_story: --- 
cf_move_to_rally: --- 
cf_rally_id: '10040878322' 
cf_rally_url: https://trial.rallydev.com/slm/#/detail/defect/10040878322 
cf_test2: --- 
cf_update_rally: --- 
classification: Unclassified 
component: Garbage 
creation_time: 2011-08-25T17:06:00Z 
creator: 
name: integrations 
real_name: Integrations 
id: 37000 
is_cc_accessible: 1 
is_confirmed: 1 
is_creator_accessible: 1 
last_change_time: 2013-01-07T16:09:43Z 
op_sys: Linux 
platform: PC 
priority: P5 
product: Garbage 
qa_contact: 
name: ~ 
ref: http://vmubu11bugz40.f4tech.com:3000/bug/1 
severity: enhancement 
status: CONFIRMED 
summary: Initial landing on moon causes dust clouds 
target_milestone: --- 
version: unspecified 

Note: You may also use an alternate URL which contains your credentials as follows: 
http://localhost:3000/bug/1?username=YourUsername@YourCompany.com&password=YourPassword 

 

5) If the Bugzilla API is installed properly, one of these two URLs will be accessible: 

 

(Again, please use your value for localhost:port) 

http://localhost:3000/configuration 
-- or -- 
http://localhost:3000/configuration?username=YourUsername@YourCompany.com&password=YourPassword 

The output in the browser should look something like; 
--- 
announcement: '' 
field: 
alias: 
description: Alias 
is_active: !!perl/scalar:JSON::XS::Boolean 1 
type: 1 
assigned_to: 
description: Assignee 
is_active: !!perl/scalar:JSON::XS::Boolean 1 
type: 0 
..... 
version: 
- unspecified 
version: 4.0.2 

 

6) The "json_pure" Ruby Gem must be installed on your system.  And it should be version 1.2.4 (that is the version which passed all of our Bugzilla tests). 

To view the Ruby Gems installed on your system, use this command: 
gem list 

 

7) If your site uses a proxy server to connect to Bugzilla: 
  • The connector itself does not have the capability to use proxy authentication. 
  • Your IT department may be able to enable access to your Bugzilla server if a proxy is involved. 

 

8) What version of Bugzilla API have you installed? 
Please note that we have tested 0.9 and 1.0 only. 

 

9) There is a custom field which must be created in Bugzilla, which will contain the Rally ID of any bug copied from Rally to Bugzilla. 
The "Type:" of this field must be "Free Text", and NOT the somewhat mis-leading "Bug ID" type, 
which is the default type used if "Free Text" is not specifically selected. 
 
If you have any questions, please feel free to post your question to Rally Success Community - Answers for help from other Rallyers. 

Outcomes