Setting up Elastiscsearch fails: Don't know how to build task 'zammad:seachindex:rebuild'

[itkfm]

Infos:

• Used Zammad version: zammad/unknown,now 5.1.1-1655802449.f7f1068b.bullseye amd64
• Used Zammad installation type: package
• Operating system: Debian 11 bullseye
• Browser + version: GNU bash, version 5.1.4(1)-release (x86_64-pc-linux-gnu)

Expected behavior:

• Search index is built

Actual behavior:

# zammad run rake zammad:searchindex:rebuild --trace
rake aborted!
Don't know how to build task 'zammad:searchindex:rebuild' (See the list of available tasks with `rake --tasks`)
Did you mean?  zammad:db:rebuild
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/lib/rake/task_manager.rb:59:in `[]'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:159:in `invoke_task'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:116:in `block (2 levels) in top_level'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:116:in `each'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:116:in `block in top_level'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:125:in `run_with_threads'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:110:in `top_level'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:83:in `block in run'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:186:in `standard_exception_handling'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/lib/rake/application.rb:80:in `run'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
/opt/zammad/vendor/bundle/ruby/2.7.0/bin/rake:23:in `load'
/opt/zammad/vendor/bundle/ruby/2.7.0/bin/rake:23:in `<top (required)>'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/cli/exec.rb:58:in `load'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/cli/exec.rb:58:in `kernel_load'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/cli/exec.rb:23:in `run'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/cli.rb:483:in `exec'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/cli.rb:31:in `dispatch'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/cli.rb:25:in `start'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/exe/bundle:48:in `block in <top (required)>'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/friendly_errors.rb:103:in `with_friendly_errors'
/opt/zammad/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/exe/bundle:36:in `<top (required)>'
/opt/zammad/bin/bundle:121:in `load'
/opt/zammad/bin/bundle:121:in `<main>'

Steps to reproduce the behavior:

• run zammad run rake zammad:searchindex:rebuild --trace

[MrGeneration]

@itkfm

• Used Zammad version: zammad/unknown,now 5.1.1-1655802449.f7f1068b.bullseye amd64

How about you update to Zammad 5.2 before using a namespace changed command of 5.2?

[itkfm]

Thanks for the hint.

Forgive me my ignorance, but this is a fresh installation. Seems like 5.2 didn’t make it to the package repository at the time of installation while the new docs got rolled out already…

[MrGeneration]

Debian 11 package built for Zammad 5.2 has finished 42 minutes ago.

The documentation update was synchronous to the release roughly 3 hours ago.
Packager takes some time so.