Content
Upgrade from 5.0.16 to 5.0.17 fails at openproject configure
Added by Jürgen Weiss about 9 years ago
Hi
when trying to upgrade my packaged installation from 5.0.16 to 5.0.17 (on Ubuntu 14.04 LTS) the “aptitude safe-upgrade” is fine,
but the “openproject configure” fails with below output.
Thanks for any help.
↳ SettingSeeder
***** Skipping settings as all settings already exist in the db
rake aborted!
NoMethodError: undefined method `namespace_name’ for BasicData::ProjectTypeSeeder:Class
/opt/openproject/app/seeders/composite_seeder.rb:65:in `block in discovered_seeder_classes’
/opt/openproject/app/seeders/composite_seeder.rb:65:in `reject’
/opt/openproject/app/seeders/composite_seeder.rb:65:in `discovered_seeder_classes’
/opt/openproject/app/seeders/composite_seeder.rb:53:in `discovered_seeders’
/opt/openproject/app/seeders/composite_seeder.rb:35:in `seed_data!’
/opt/openproject/app/seeders/seeder.rb:33:in `seed!’
/opt/openproject/app/seeders/root_seeder.rb:54:in `block in do_seed!’
/opt/openproject/vendor/bundle/ruby/2.1.0/gems/activerecord-4.2.5.2/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction’
/opt/openproject/vendor/bundle/ruby/2.1.0/gems/activerecord-4.2.5.2/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction’
/opt/openproject/vendor/bundle/ruby/2.1.0/gems/activerecord-4.2.5.2/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction’
/opt/openproject/vendor/bundle/ruby/2.1.0/gems/activerecord-4.2.5.2/lib/active_record/transactions.rb:220:in `transaction’
/opt/openproject/vendor/bundle/ruby/2.1.0/bundler/gems/transactional_lock-6948b1d446db/lib/transactional_lock/active_record_patches.rb:12:in `block in transaction’
/opt/openproject/vendor/bundle/ruby/2.1.0/bundler/gems/transactional_lock-6948b1d446db/lib/transactional_lock/transaction_wrapper.rb:21:in `wrap’
/opt/openproject/vendor/bundle/ruby/2.1.0/bundler/gems/transactional_lock-6948b1d446db/lib/transactional_lock/active_record_patches.rb:11:in `transaction’
/opt/openproject/app/seeders/root_seeder.rb:51:in `do_seed!’
/opt/openproject/app/seeders/root_seeder.rb:47:in `seed_data!’
/opt/openproject/app/seeders/seeder.rb:33:in `seed!’
/opt/openproject/db/seeds.rb:30:in `<top (required)>’
/opt/openproject/vendor/bundle/ruby/2.1.0/gems/activesupport-4.2.5.2/lib/active_support/dependencies.rb:268:in `load’
/opt/openproject/vendor/bundle/ruby/2.1.0/gems/activesupport-4.2.5.2/lib/active_support/dependencies.rb:268:in `block in load’
/opt/openproject/vendor/bundle/ruby/2.1.0/gems/activesupport-4.2.5.2/lib/active_support/dependencies.rb:240:in `load_dependency’
/opt/openproject/vendor/bundle/ruby/2.1.0/gems/activesupport-4.2.5.2/lib/active_support/dependencies.rb:268:in `load’
/opt/openproject/vendor/bundle/ruby/2.1.0/gems/railties-4.2.5.2/lib/rails/engine.rb:547:in `load_seed’
/opt/openproject/vendor/bundle/ruby/2.1.0/gems/activerecord-4.2.5.2/lib/active_record/tasks/database_tasks.rb:250:in `load_seed’
/opt/openproject/vendor/bundle/ruby/2.1.0/gems/activerecord-4.2.5.2/lib/active_record/railties/databases.rake:183:in `block (2 levels) in <top (required)>’
Tasks: TOP => db:seed
(See full trace by running task with —trace)
Replies (5)
Hey Jürgen,
A bug may have snuck into the data seeding process which should only matter on first installations. I’m trying to recreate your issue on my Ubuntu machine and will let you know as soon as I can.
Best,
Oliver
Hi again,
we’ve identified the issue and are pushing a new 5.0.17 release. It’s still building on packager, once that’s completed, another upgrade & configure should run fine. (Edit: Build completed).
https://packager.io/gh/opf/openproject-ce/build_runs/136
Sorry for the inconveniences.
Best,
Oliver
Hi Oliver,
thanks a lot. Will try when the build is available and report back.
Regards, Jürgen
Hi,
problem resolved. Thanks for the super-fast solution.
Regards, Jürgen
Hi,
i had the same problem. After the updates does this work again.
Regards, Stefan