Ravenbrook / Projects / Perforce Defect Tracking Integration / Issues

Perforce Defect Tracking Integration


P4DTI issue job000461

Title: Bugzilla integration doesn't support multiple Perforce servers
Status: closed
Priority: critical
Assigned user: Nick Barnes
Product: p4dti
Organization: Ravenbrook
Description: The Bugzilla integration doesn't work with multiple Perforce servers. The second replicator instance will fail.
The failure is reported with this message:
_mysql.OperationalError: (1091, "Can't DROP 'action'. Check that column/key exists")
Analysis: The code to handle changes in the P4DTI schema looks for a config item called schema_version. However, config items (rows in the p4dti_config table) are per-replicator, so if there is more than one replicator, the schema_version config item written by one replicator won't be found by the other. So the second replicator will think that the schema is version 0 (no schema_version) and will try to upgrade it. This upgrade will fail with the message quoted above.
How found: customer
Evidence: <http://info.ravenbrook.com/mail/2002/02/06/01-03-39/0.txt>
Observed in: 1.4.0
Introduced in: 0.0.0
Test procedure: none
Created by: Nick Barnes
Created on: 2002-02-06 14:16:19
Last modified by: Nick Barnes
Last modified on: 2002-04-09 11:33:23
History: 2002-02-06 NB Created.

Fixes

Change Effect Date User Description
26878 closed 2002-02-22 12:07:29 gdr The P4DTI schema version doesn't depend on the replicator and server identifiers.

Generated at 2010-03-09 17:12:03 by $Id: //info.ravenbrook.com/infosys/cgi/issue.cgi#439 $

Copyright © Ravenbrook Limited. This document is provided "as is", without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this document. You may make and distribute verbatim copies of this document provided that you do not charge a fee for this document or for its distribution.

Ravenbrook / Projects / Perforce Defect Tracking Integration / Issues