Hi, I am trying to upgrade my Discourse install from image tag 3.0.6 to 3.1.1 but am seeing the below issue. I know I am using what is deemed an unsupported installation with the Bitnami Helm Chart in a Kubernetes cluster but I am completely stuck on how to resolve. The error below is being emitted when I try to upgrade from an off the shelf Discourse install (no additional plugins added) to the latest version. Looking at the forum I can see this post - Upgrade failed (NoMethodError: undefined method `register_bookmarkable' for Bookmark:Class) - but it talks about the discourse-data-explorer plugin which as mentioned above is not installed in the default Bitnami Discourse installation. Can anyone help? Thanks, Steve discourse 07:39:04.07 INFO ==> Running database migrations rake aborted! NoMethodError: undefined method `register_bookmarkable' for Bookmark:Class /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/activerecord-7.0.5.1/lib/active_record/dynamic_matchers.rb:22:in `method_missing' /opt/bitnami/discourse/plugins/chat/plugin.rb:261:in `block (2 levels) in activate!' /opt/bitnami/discourse/lib/plugin/instance.rb:1351:in `reloadable_patch' /opt/bitnami/discourse/plugins/chat/plugin.rb:250:in `block in activate!' /opt/bitnami/discourse/lib/plugin/instance.rb:526:in `block in notify_after_initialize' /opt/bitnami/discourse/lib/plugin/instance.rb:524:in `each' /opt/bitnami/discourse/lib/plugin/instance.rb:524:in `notify_after_initialize' /opt/bitnami/discourse/config/application.rb:230:in `each' /opt/bitnami/discourse/config/application.rb:230:in `block (2 levels) in ' /opt/bitnami/discourse/lib/plugin.rb:6:in `initialization_guard' /opt/bitnami/discourse/config/application.rb:230:in `block in ' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.5.1/lib/active_support/lazy_load_hooks.rb:92:in `block in execute_hook' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.5.1/lib/active_support/lazy_load_hooks.rb:85:in `with_execution_control' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.5.1/lib/active_support/lazy_load_hooks.rb:90:in `execute_hook' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.5.1/lib/active_support/lazy_load_hooks.rb:76:in `block in run_load_hooks' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.5.1/lib/active_support/lazy_load_hooks.rb:75:in `each' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.5.1/lib/active_support/lazy_load_hooks.rb:75:in `run_load_hooks' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.5.1/lib/rails/application/finisher.rb:87:in `block in ' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.5.1/lib/rails/initializable.rb:32:in `instance_exec' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.5.1/lib/rails/initializable.rb:32:in `run' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.5.1/lib/rails/initializable.rb:61:in `block in run_initializers' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.5.1/lib/rails/initializable.rb:60:in `run_initializers' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.5.1/lib/rails/application.rb:372:in `initialize!' /opt/bitnami/discourse/config/environment.rb:7:in ` ' :38:in `require' :38:in `require' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/zeitwerk-2.6.10/lib/zeitwerk/kernel.rb:38:in `require' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.5.1/lib/rails/application.rb:348:in `require_environment!' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.5.1/lib/rails/application.rb:506:in `block in run_tasks_blocks' /opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/rake-13.0.6/exe/rake:27:in ` ' /opt/bitnami/ruby/bin/bundle:25:in `load' /opt/bitnami/ruby/bin/bundle:25:in ` '

That’s right. It was initially a separate plugin but has since been bundled in with core, so no need to install it separately any more.

Thanks @JammyDodger Is there a way to disable core plugins at startup so I can test if the Chat plugin is the issue? The Bitnami chart allows me to pass a list of plugins and it will run the command RAILS_ENV=production bundle exec rake plugin:install repo={{ $plugin }} for each plugin I supply BUT I think that will be on top of the core plugins. I will look at the standard installation again - we deploy all our 3rd party apps using Helm charts in our kubernetes cluster but maybe it makes sense to make an exception for Discourse if kubernetes and helm support are a long way off.

Just a quick update, it seems that performing an upgrade from a pre-3.0.0 version allows the upgrade to work i.e 2.8.11 → 3.0.6 → 3.1.1 I am not sure if this is a pure accident or not but trying to upgrade from 3.0.6 straight to 3.1.1 does not work. Interestingly the Chat plugin does not even show in my Discourse deployment after this upgrade path. It is thought it is still treated as an external plugin rather than being part of the core product. Anyone know if the Chat plugin is correct with this upgrade path or is something very wrong that it is not present!

Have you enabled it? Admin → Settings: [image] It’s still a plugin but shipped with core, so enabling it works slightly differently.

I will double check my install but I don’t even see the flag. I don’t see the plugin code on the server either with this upgrade whereas if I start with v3.0.6 I’m sure I do but will double check it all.

If you are cloning the official repo, it’s included, here’s the current contents of stable branch: discourse/plugins/chat at stable · discourse/discourse · GitHub

@merefield - So I just checked, if I upgrade from version 2.8.11 to 3.0.6 the Chat plugin is not available. As mentioned above, I am using the Bitnami Helm chart to deploy Discourse which I know is not supported but what is interesting is if I start with version 3.0.6 the Chat plugin is present.

Did you remove the chat plugin from your app.yml prior to updating? You should.

I didn’t do anything with the Chat plugin but that is not to say that the scrips Bitnami use to build their version of the Discourse image is not impacting it. This is the Bitnami Discourse repo - containers/bitnami/discourse at main · bitnami/containers · GitHub and this is how they build the Docker image - https://github.com/bitnami/containers/blob/main/bitnami/discourse/3/debian-11/Dockerfile

My suggestion? Just dump a backup and move to the standard install.

Discourse v3.0.6 to v3.1.1 upgrade error - undefined method `register_bookmarkable' for Bookmark:Class

Product Support Self-hosting

Firepup650 (Firepup Sixfifty) February 22, 2024, 6:47pm 24

Does Kubernetes allow you to do a manual install? If so, you could do a standard install that way. (I’ve never tried it, so I don’t know how Kubernetes works)

Topic		Replies	Views
Upgrade failed (NoMethodError: undefined method `register_bookmarkable' for Bookmark:Class) Self-hosting	4	1377	October 2, 2023
Discourse-chat-integration prevents upgrade Product Support chat-integration	7	475	September 7, 2024
Error when upgrading to the latest version due to third party plugin Self-hosting	3	733	October 2, 2019
What does it mean if Discourse is installed via Bitnami? Self-hosting unsupported-install	15	3992	October 28, 2017
Error upgrading 2.3.5 to 2.4.2 Self-hosting unsupported-install	16	1255	May 4, 2020

Discourse v3.0.6 to v3.1.1 upgrade error - undefined method `register_bookmarkable' for Bookmark:Class

Related topics