ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Migrating from Redmine 1.3: Table permissions not found (Bug #1015)

Added by Sebastian Dreßler at 2012-05-18 07:50 am. Updated at 2012-05-19 01:25 pm.

Status:Closed Start date:2012-05-18
Priority:High Due date:
Assignee:- % Done:

0%
Category:-
Target version:-
Remote issue URL: Affected version:3.1.0

Description

When migrating from Redmine 1.3 to ChiliProject 3.1 I get the following error message when executing 

bundle exec rake db:migrate RAILS_ENV=production
:

rake aborted!
Could not find table 'permissions'

This is triggered within 

014_add_queries_permissions.rb
. However, it makes no sense to me, because the permissions table gets created and is dropped afterwards when creating a completely new database.

History

#1
Updated by Felix Schäfer at 2012-05-18 07:27 pm

Especially because this migration should have been run for Redmine before, could you see if '014' is in the schema_migrations table of your DB?

#2
Updated by Sebastian Dreßler at 2012-05-19 09:16 am

No, no entry regarding 014 in schema_migrations.

#3
Updated by Felix Schäfer at 2012-05-19 09:21 am

Then there's a problem with your DB, there should be the number of all the migrations in db/migrate from your Redmine even before you start migrating to ChiliProject.

#4
Updated by Sebastian Dreßler at 2012-05-19 09:43 am

Would it be possible to setup a completely new DB and copy the old data without copying schema_migrations?

#5
Updated by Felix Schäfer at 2012-05-19 09:52 am

Not really reliably, no.

My best guess would be to repair your Redmine install before upgrading it. The tricky part here is to add the numbers of the migrations you are sure have already run to the schema_migrations table. There's no real clue other than studying the migrations and the DB to know which have run though. In any case, try this on a copy first!

(If you need further help with this, I could get you in touch with Redmine "specialists" in Berlin)

#6
Updated by Sebastian Dreßler at 2012-05-19 10:08 am

Getting some professional help with this would be nice, right now I'm not able to upgrade to anything.

#7
Updated by Sebastian Dreßler at 2012-05-19 10:41 am

I was able to repair the DB, it seems to work now. So this issue can be closed. Thanks for your help.

#8
Updated by Felix Schäfer at 2012-05-19 01:25 pm

Sebastian Dreßler wrote:

I was able to repair the DB, it seems to work now. So this issue can be closed. Thanks for your help.

Great to hear, I hope the rest of the upgrade goes well :-)

  • Status changed from Open to Closed

Also available in: Atom PDF