[opensuse-buildservice] API server database migration fails (unstable upgrades)
![](https://seccdn.libravatar.org/avatar/407895fd75a9e2ca2ee5bee1064c6345.jpg?s=120&d=mm&r=g)
Hi, I've been working with an OBS installation from openSUSE:Tools:Unstable, and went through several upgrades. During each upgrade, I am instructed to run the database migration scripts. For the API server database, it always failed with this error. Mysql::Error: Table 'api_production.issue_trackers' doesn't exist: ALTER TABLE ` issue_trackers` ADD `kind` ENUM('bugzilla', 'cve', 'fate', 'trac', 'launchpad', 'sourceforge') AFTER `name` Finally, after updating to obs-api 2.2.107, I'm in a corner because the API server needs some new table to serve commit requests. Should I fix the database manually and how, or should the migration script account for earlier installations of unstable OBS? I'm attaching the output of 'rake db:migrate --trace'. Best regards, Mikhail
![](https://seccdn.libravatar.org/avatar/84ee0bcf221e4fb2b4741908022b82fb.jpg?s=120&d=mm&r=g)
Am Donnerstag, 15. Dezember 2011, 00:22:38 schrieb Mikhail Zabaluev:
Hi,
I've been working with an OBS installation from openSUSE:Tools:Unstable, and went through several upgrades. During each upgrade, I am instructed to run the database migration scripts. For the API server database, it always failed with this error.
Mysql::Error: Table 'api_production.issue_trackers' doesn't exist: ALTER TABLE ` issue_trackers` ADD `kind` ENUM('bugzilla', 'cve', 'fate', 'trac', 'launchpad', 'sourceforge') AFTER `name`
This table should have been created either by "rake db:setup" when you installed a fresh 2.2 release or via the migration from 28th July. Do you have an idea, when you did a fresh setup of this database ? bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (2)
-
Adrian Schröter
-
Mikhail Zabaluev