| Title | Bugzilla integration upgrade fails if you change the replicator id |
| Status | suspended |
| Priority | essential |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | If you upgrade the Bugzilla integration (say from release 1.1.1 to release 1.1.4) and simultaneously change the replicator id, then the replicator stops with an error. The output of the P4DTI looks like this: 2001-08-02 15:42:24 UTC (P4DTI-1193) replicator0 Old P4DTI/Bugzilla schema version 0 detected; altering tables to upgrade to schema version 1. [...] _mysql.OperationalError: (1091, "Can't DROP 'action'. Check that column/key exists") |
| Analysis | The replicator is storing the schema_version configuration parameter on a per-replicator basis. It should store only one schema_version. Note that this bug will affect people running multiple replicators who try to upgrade. They may upgrade one replicator but not the other and neither will notice. Or they may upgrade both and find that the second upgrade fails to work. Should document the error message in the AG just in case. |
| How found | customer |
| Evidence | <http://info.ravenbrook.com/mail/2001/08/02/15-52-42/0.txt> |
| Observed in | 1.1.4 |
| Introduced in | 1.1.2 |
| Created by | Gareth Rees |
| Created on | 2001-08-02 21:13:23 |
| Last modified by | Nick Barnes |
| Last modified on | 2018-07-05 17:27:45 |
| History | 2001-08-02 GDR Created. 2018-07-05 NB Suspended because the P4DTI is obsolete. |