No, reinstalling the memcached plugin seems to result in this error. On Tuesday, December 12, 2017 at 7:59:06 AM UTC-6, Iain Walmsley wrote: > > I've encountered the same problem with the default hostgroup, but even > when removing this and still using memcached I see the same issue; > > rake aborted! > No such middleware to insert after: > ActionDispatch::Session::ActiveRecordStore > /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/stack.rb:125:in > > `assert_index' > /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.2.5.1/lib/action_dispatch/middleware/stack.rb:96:in > > `insert_after' > /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/configuration.rb:68:in > > `block in merge_into' > /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/configuration.rb:67:in > > `each' > /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/configuration.rb:67:in > > `merge_into' > /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:501:in > > `app' > /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application/finisher.rb:34:in > > `block in <module:Finisher>' > /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in > > `instance_exec' > /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in > > `run' > /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:55:in > > `block in run_initializers' > /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:54:in > > `run_initializers' > /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application.rb:352:in > > `initialize!' > /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in > > `public_send' > /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in > > `method_missing' > /usr/share/foreman/config/environment.rb:5:in `<top (required)>' > > [root@localhost foreman]# rpm -qa | grep -i foreman > foreman-cli-1.16.0-1.el7.noarch > tfm-rubygem-foreman_memcache-0.0.6-1.fm1_15.el7.noarch > foreman-installer-1.16.0-1.el7.noarch > foreman-1.16.0-1.el7.noarch > tfm-rubygem-hammer_cli_foreman-0.11.0-1.el7.noarch > tfm-rubygem-foreman_setup-5.0.0-1.fm1_13.el7.noarch > foreman-selinux-1.16.0-1.el7.noarch > foreman-debug-1.16.0-1.el7.noarch > foreman-postgresql-1.16.0-1.el7.noarch > > Removing memcached seems to resolve the issue, are you installing > memcached successfully with 1.16? > > On Thursday, December 7, 2017 at 11:25:02 PM UTC, Jeff Stasko wrote: >> >> But I had to remove tfm-rubygem-foreman_default_hostgroup >> >> >> My fix is in this post >> >> https://groups.google.com/forum/m/?source=mog&gl=us#!topic/foreman-users/bWfJJ-xyzGE >> >
-- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
