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.

migration fails from 1.1.0 to 2.1.1 (Bug #568)

Added by pille palle at 2011-08-08 01:08 pm. Updated at 2011-09-07 05:02 pm.

Status:Needs more information Start date:2011-08-08
Priority:Normal Due date:
Assignee:- % Done:

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

Description

from mnemonikk:
We hit a problem while upgrading from version 1.1.0 to 2.1.1.
The migration MergeWikiVersionsWithJournals caused an exception because the attribute "changes" was passed as a string, already serialized to YAML, while ActiveRecord was expecting a hash.
I think this should be fixed by removing .to_yaml from line 33 in
db/migrate/20100804112053_merge_wiki_versions_with_journals.rb.

History

#1
Updated by Aleksey Zapparov at 2011-08-08 03:42 pm

I believe you met same problem as I did #554, running Ruby 1.9.2. Use Ruby 1.8.7 on migration. The problem is that 1.x branch was not supposed to work with Ruby 1.9.2

#2
Updated by pille palle at 2011-08-08 03:58 pm

Aleksey Zapparov wrote:

I believe you met same problem as I did #554, running Ruby 1.9.2. Use Ruby 1.8.7 on migration.

i doubt that. i'm running:

ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2011.03

it may be a model-change somewhere inbetween listed chiliproject versions.

#3
Updated by Holger Just at 2011-09-04 09:07 pm

I could not observed your described behavior. If you still observer this issue, please provide examples of your data which show the wrong behavior.

  • Status changed from Open to Needs more information

#4
Updated by A Samz at 2011-09-07 02:15 pm

For what it's worth I experienced the same problem. We upgrade from Redmine 1.1.2 to ChiliProject 1.5.2 (We did this because the DB migration failed for the later versions.) Trying to upgrade ChiliProject from 1.5.2 to 2.X.X caused the db migration to fail with an output as seen in issue #554. This is preventing us from using ChiliProject.

#5
Updated by pille palle at 2011-09-07 02:59 pm

as we solved the problem, we don't observe it anymore.
others may still be hit by this one.
i'd like to add that our instance was migrated from redmine to chiliproject-1.1.0 in the past.

if you're interested in any particular data, please let me know. our whole dump is about 85M and i don't like to disclose it completely.

#6
Updated by A Samz at 2011-09-07 04:03 pm

pille palle wrote:

as we solved the problem, we don't observe it anymore.

Can you say what you did to get around, or fix, the issue?

#7
Updated by pille palle at 2011-09-07 05:02 pm

from the original description:
"this should be fixed by removing .to_yaml from line 33 in
db/migrate/20100804112053_merge_wiki_versions_with_journals.rb"

Also available in: Atom PDF