Installed plugin foreman_column_view and dependencies - now foreman doesn't start anymore... :(

Another question/problem:
I added the foreman_column_view plugin, and its dependencies, and after that my foreman doesn’t start anymore. I’ve even removed the gem 'foreman_column_view' from /usr/share/foreman/bundle.d/Gemfile.local.rb, but still it doesn’t start.
I think I got some faulty gems installed when installing the column_view plugin gem, but I have no idea which might have created this problem.
Problem:
Foreman doesn’t start

Expected outcome:
Restart of foreman
Foreman and Proxy versions:
3.1
Foreman and Proxy plugin versions:
foreman_column_view 0.4
Distribution and version:
RHEL 7.9
Other relevant data:

Dec 27 14:10:05 redacted foreman hostname foreman[22080]: from /opt/rh/rh-ruby27/root/usr/local/share/gems/gems/railties-7.0.0/lib/rails/commands/server/server_command.rb:134:in `tap'
Dec 27 14:10:05 redacted foreman hostname foreman[22080]: from /opt/rh/rh-ruby27/root/usr/local/share/gems/gems/railties-7.0.0/lib/rails/commands/server/server_command.rb:134:in `perform'
Dec 27 14:10:05 redacted foreman hostname foreman[22080]: from /opt/rh/rh-ruby27/root/usr/local/share/gems/gems/thor-1.1.0/lib/thor/command.rb:27:in `run'
Dec 27 14:10:05 redacted foreman hostname foreman[22080]: from /opt/rh/rh-ruby27/root/usr/local/share/gems/gems/thor-1.1.0/lib/thor/invocation.rb:127:in `invoke_command'
Dec 27 14:10:05 redacted foreman hostname foreman[22080]: from /opt/rh/rh-ruby27/root/usr/local/share/gems/gems/thor-1.1.0/lib/thor.rb:392:in `dispatch'
Dec 27 14:10:05 redacted foreman hostname foreman[22080]: from /opt/rh/rh-ruby27/root/usr/local/share/gems/gems/railties-7.0.0/lib/rails/command/base.rb:87:in `perform'
Dec 27 14:10:05 redacted foreman hostname foreman[22080]: from /opt/rh/rh-ruby27/root/usr/local/share/gems/gems/railties-7.0.0/lib/rails/command.rb:48:in `invoke'
Dec 27 14:10:05 redacted foreman hostname foreman[22080]: from /opt/rh/rh-ruby27/root/usr/local/share/gems/gems/railties-7.0.0/lib/rails/commands.rb:18:in `<top (required)>'
Dec 27 14:10:05 redacted foreman hostname foreman[22080]: from /opt/rh/rh-ruby27/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:158:in `require'
Dec 27 14:10:05 redacted foreman hostname foreman[22080]: from /opt/rh/rh-ruby27/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:158:in `rescue in require'
Dec 27 14:10:05 redacted foreman hostname foreman[22080]: from /opt/rh/rh-ruby27/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:147:in `require'
Dec 27 14:10:05 redacted foreman hostname foreman[22080]: from /usr/share/foreman/bin/rails:9:in `<main>'
Dec 27 14:10:05 redacted foreman hostname foreman[22080]: /opt/rh/rh-ruby27/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:83:in `require': cannot load such file -- rails/commands (LoadError)
Dec 27 14:10:05 redacted foreman hostname foreman[22080]: from /opt/rh/rh-ruby27/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:83:in `require'
Dec 27 14:10:05 redacted foreman hostname foreman[22080]: from /usr/share/foreman/bin/rails:9:in `<main>'
Dec 27 14:10:05 redacted foreman hostname systemd[1]: Unit foreman.service entered failed state.
Dec 27 14:10:05 redacted foreman hostname systemd[1]: foreman.service failed.

Ok, it turns out I had gotten a bunch of too new gems installed - which created the problem.

activesupport-7.0.0
actioncable-7.0.0
actionmailer-7.0.0
actionpack-7.0.0
actionview-7.0.0
activejob-7.0.0
activemodel-7.0.0
railties-7.0.0
activerecord-7.0.0
actionmailbox-7.0.0
actiontext-7.0.0
activestorage-7.0.0
rails-7.0.0

After removing the 7.0.0-version of all these I got it to work again. :slight_smile: