Project

General

Profile

Bug #22743

Update failed at migrate_foreman: "can't modify frozen Array"

Added by Ivan Necas over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Upgrades
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1549502

Description of problem:
At some circumstances (not clear by the time of filing this bug), the upgrade to 6.3 can fail with the following error in migrate_foreman step;

[DEBUG 2018-02-24 10:05:07 main] API controllers newer than Apipie cache! Run apipie:cache rake task to regenerate cache.
[DEBUG 2018-02-24 10:05:22 main] rake aborted!
[DEBUG 2018-02-24 10:05:22 main] can't modify frozen Array
[DEBUG 2018-02-24 10:05:22 main] /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.4.5.58/lib/katello/engine.rb:147:in `block in <class:Engine>'
[DEBUG 2018-02-24 10:05:22 main] /opt/rh/rh-ror42/root/usr/share/gems/gems/railties-4.2.6/lib/rails/initializable.rb:30:in `instance_exec'
[DEBUG 2018-02-24 10:05:22 main] /opt/rh/rh-ror42/root/usr/share/gems/gems/railties-4.2.6/lib/rails/initializable.rb:30:in `run'
[DEBUG 2018-02-24 10:05:22 main] /opt/rh/rh-ror42/root/usr/share/gems/gems/railties-4.2.6/lib/rails/initializable.rb:55:in `block in run_initializers'
[DEBUG 2018-02-24 10:05:22 main] /opt/rh/rh-ror42/root/usr/share/gems/gems/railties-4.2.6/lib/rails/initializable.rb:54:in `run_initializers'
[DEBUG 2018-02-24 10:05:22 main] /opt/rh/rh-ror42/root/usr/share/gems/gems/railties-4.2.6/lib/rails/application.rb:352:in `initialize!'
[DEBUG 2018-02-24 10:05:22 main] /opt/rh/rh-ror42/root/usr/share/gems/gems/railties-

How reproducible:
Reproduced at one user, works locally or with other users


Related issues

Related to Foreman - Bug #21295: Slow start of rails environment when starting passenger or foreman-tasksClosed2017-10-11

Associated revisions

Revision 5c582b87 (diff)
Added by Ivan Necas over 3 years ago

Fixes #22743 - ensure proper ordering on registering relaod paths

In some cases, the initializers were running in wrong order (running
'katello.paths' after 'sooner_routes_load', which lead to `can't modify
frozen Array`.

Being explicit about the ordering should help making sure we don't run
into the issue.

This was not reproduced locally, was proved at the user the patch
resolved the issue.

History

#1 Updated by Ivan Necas over 3 years ago

  • Assignee set to Ivan Necas
  • Status changed from New to Assigned
  • Subject changed from Upgrade from sat6.2 -> 6.3 failed at migrate_foreman: "can't modify frozen Array" to Update failed at migrate_foreman: "can't modify frozen Array"

#2 Updated by Ivan Necas over 3 years ago

  • Related to Bug #21295: Slow start of rails environment when starting passenger or foreman-tasks added

#3 Updated by The Foreman Bot over 3 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/7217 added

#4 Updated by Ivan Necas over 3 years ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

#5 Updated by John Mitsch over 3 years ago

  • Legacy Backlogs Release (now unused) set to 284

Also available in: Atom PDF