Actions
Defect #15538
closedUpgrading from 2.3.3 to 2.4.1 breaks
Status:
Closed
Priority:
Urgent
Assignee:
-
Category:
Administration
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Invalid
Affected version:
Description
I just tried to upgrade my 2.3.3 instance to 2.4.1
I always upgrade as it is decribed in http://www.redmine.org/projects/redmine/wiki/RedmineUpgrade
Running rake db:migrate RAILS_ENV=production gives me an error now.
There seems to be a bug somewhere in the migration routine... Maybe you can help me out with a workaround?
#rake db:migrate RAILS_ENV=production == CreateQueriesRoles: migrating ============================================= -- create_table(:queries_roles, {:id=>false}) -> 0.0320s -- add_index(:queries_roles, [:query_id, :role_id], {:unique=>true, :name=>:queries_roles_ids}) -> 0.0416s == CreateQueriesRoles: migrated (0.0743s) ==================================== == AddQueriesVisibility: migrating =========================================== -- add_column(:queries, :visibility, :integer, {:default=>0}) -> 0.1533s -- remove_column(:queries, :is_public) -> 0.0411s == AddQueriesVisibility: migrated (0.2224s) ================================== == CreateCustomFieldsRoles: migrating ======================================== -- create_table(:custom_fields_roles, {:id=>false}) -> 0.0101s -- add_index(:custom_fields_roles, [:custom_field_id, :role_id], {:unique=>true, :name=>:custom_fields_roles_ids}) -> 0.0274s == CreateCustomFieldsRoles: migrated (0.0446s) =============================== == AddQueriesOptions: migrating ============================================== -- add_column(:queries, :options, :text) -> 0.0109s == AddQueriesOptions: migrated (0.0110s) ===================================== == AddUsersMustChangePasswd: migrating ======================================= -- add_column(:users, :must_change_passwd, :boolean, {:default=>false, :null=>false}) -> 0.0163s == AddUsersMustChangePasswd: migrated (0.0164s) ============================== == RemoveEolsFromAttachmentsFilename: migrating ============================== == RemoveEolsFromAttachmentsFilename: migrated (0.0593s) ===================== == SupportForMultipleCommitKeywords: migrating =============================== rake aborted! An error has occurred, all later migrations canceled: undefined method `commit_update_keywords=' for #<Class:0x000000048407e8> Tasks: TOP => db:migrate (See full trace by running task with --trace)
Running it with the trace command gives
#rake db:migrate RAILS_ENV=production --trace ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Invoke db:load_config (first_time) ** Execute db:load_config ** Execute db:migrate == SupportForMultipleCommitKeywords: migrating =============================== rake aborted! An error has occurred, all later migrations canceled: undefined method `commit_update_keywords=' for #<Class:0x000000033d4610> /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/dynamic_matchers.rb:55:in `method_missing' /srv/redmine/redmine-2.4.1/db/migrate/20131004113137_support_for_multiple_commit_keywords.rb:9:in `up' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/migration.rb:410:in `block (2 levels) in migrate' /usr/lib64/ruby/1.9.1/benchmark.rb:280:in `measure' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/migration.rb:410:in `block in migrate' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/connection_adapters/abstract/connection_pool.rb:129:in `with_connection' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/migration.rb:389:in `migrate' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/migration.rb:528:in `migrate' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/migration.rb:720:in `block (2 levels) in migrate' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/migration.rb:777:in `call' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/migration.rb:777:in `ddl_transaction' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/migration.rb:719:in `block in migrate' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/migration.rb:700:in `each' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/migration.rb:700:in `migrate' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/migration.rb:570:in `up' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/migration.rb:551:in `migrate' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.15/lib/active_record/railties/databases.rake:193:in `block (2 levels) in <top (required)>' /usr/lib64/ruby/1.9.1/rake/task.rb:205:in `call' /usr/lib64/ruby/1.9.1/rake/task.rb:205:in `block in execute' /usr/lib64/ruby/1.9.1/rake/task.rb:200:in `each' /usr/lib64/ruby/1.9.1/rake/task.rb:200:in `execute' /usr/lib64/ruby/1.9.1/rake/task.rb:158:in `block in invoke_with_call_chain' /usr/lib64/ruby/1.9.1/monitor.rb:211:in `mon_synchronize' /usr/lib64/ruby/1.9.1/rake/task.rb:151:in `invoke_with_call_chain' /usr/lib64/ruby/1.9.1/rake/task.rb:144:in `invoke' /usr/lib64/ruby/1.9.1/rake/application.rb:116:in `invoke_task' /usr/lib64/ruby/1.9.1/rake/application.rb:94:in `block (2 levels) in top_level' /usr/lib64/ruby/1.9.1/rake/application.rb:94:in `each' /usr/lib64/ruby/1.9.1/rake/application.rb:94:in `block in top_level' /usr/lib64/ruby/1.9.1/rake/application.rb:133:in `standard_exception_handling' /usr/lib64/ruby/1.9.1/rake/application.rb:88:in `top_level' /usr/lib64/ruby/1.9.1/rake/application.rb:66:in `block in run' /usr/lib64/ruby/1.9.1/rake/application.rb:133:in `standard_exception_handling' /usr/lib64/ruby/1.9.1/rake/application.rb:63:in `run' /usr/bin/rake:32:in `<main>' Tasks: TOP => db:migrate
Some data for my redmine instance:
Environment: Redmine version 2.3.3.stable Ruby version 1.9.3-p392 (2013-02-22) [x86_64-linux] Rails version 3.2.13 Environment production Database adapter Mysql2 Redmine plugins: redmine_charts2 0.2.1 sidebar_hide 0.0.4
Updated by Jean-Philippe Lang almost 10 years ago
- Status changed from New to Closed
- Resolution set to Invalid
You're using an obsolete config/settings.yml
. Replace yours with the one provided with 2.4.1 and re-run the migration.
Actions